{"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity 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 require for Maintenance?"}, {"role": "assistant", "content": "According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\nxamples of configuration actions to implement the guideline\n- o The examples are described at a high level as the process to implement the guideline will vary by manufacturer and smart-inverter model.\nConsult the manufacturer's documentation for specific instructions."}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy 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 Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations:\n\nIntroduction_______________________________________________________1 | |---------------------------------------------------------------------------|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| | | 1.1 | Scope | ______________________________________________________________2 | | | 1.2 | Audience | ____________________________________________________________3 | | | 1.3 | Background and Rationale | ______________________________________________3 | | | 1.4 | Organization _________________________________________________________4 | | | | 1.5 | Glossary of Terms and Acronyms_________________________________________5 | | | | | 1.5.1 Glossary_____________________________________________________________ | 5 | | | | 1.5.2 Acronyms___________________________________________________________ | 19 | | 2 | Key-Management Concepts_________________________________________21 | Key-Management Concepts_________________________________________21 | | | | 2.1 | Key Establishment____________________________________________________21 | | | | 2.2 | Key-Management Functions | ____________________________________________21 | | | 2.3 | Cryptographic Key Management Systems (CKMS) | __________________________22 | | | | 2.3.1 Central Oversight Authority | _____________________________________________ 23 | | | | 2.3.2 Key-Processing Facility(ies) | ____________________________________________ 23 | | | | 2.3.3 Service Agents_______________________________________________________ | 25 | | | | 2.3.4 Client Nodes | ________________________________________________________ 25 | | | | 2.3.5 Tokens _____________________________________________________________ | 26 | | | | 2.3.6 Public Key Infrastructure Environments ___________________________________ | 26 | | | | 2.3.7 Symmetric Key Environments | ___________________________________________ 26 | | | | 2.3.8 Hierarchies and Meshes _______________________________________________ | 27 | | | | Centralized vs."}], "metadata": {"source": "Recommendation for Key Management_ Part 2 – Best Practices for Key Management 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 Media Protection?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n3.3.5, 3. 3.3.5 |\n| with related policies, PR. 3.3.5 |\n| with related policies, PR."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security Architecture Design Process for Health Information Exchanges (HIEs) provide? (Part 2)"}, {"role": "assistant", "content": "| EXECUTIVE SUMMARY..................................................................................................\n| 1 |\n|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2.0 | INTRODUCTION ................................................................................................................ 1 | INTRODUCTION ................................................................................................................"}], "metadata": {"source": "Security Architecture Design Process for Health Information Exchanges (HIEs)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.12. Requirements for Visual Facial Image Comparison . . . . . . . . . . . .\n\ntranscription, or accessibility support) to assist the applicant in the identity\nproofing process but does not support decision-making or risk-based evaluation.\n\n13. The CSP’s policy for assessing customer experience, including the testing methods\nemployed, timing of its periodic reviews, and any specific conditions that will\ntrigger an out-of-cycle review (see Sec. 3.4)"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to 2017 NIST_ITL Cybersecurity Program Annual Report:\n\n- NIST improved two widely used guidelines that provide senior leaders with the information they need to make risk-based decisions affecting critical mission and business functions. We proposed revisions to Security and Privacy Controls for Information Systems and Organizations (Special Publication (SP) 800-53) and Risk Management Framework for Information Systems and Organizations (SP 800-37). The latter provides a closer link between risk management processes and activities at various organizational levels. It demonstrates how the Cybersecurity Framework can be implemented using established Risk Management Framework processes. Both publications will be finalized in 2018. - Reflecting a growing recognition of the link between cybersecurity and privacy risk management, we collaborated with internal and external partners to integrate privacy requirements and considerations into SP 800-53 and SP 800-37 risk management guidelines as well as our latest version of NIST's Digital Identity Guidelines (SP 800-63-3), which covers digital identity from the initial risk assessment to the deployment of federated identity solutions. These guidelines build the foundation needed to make privacy and security equal, quality attributes in trustworthy systems. We focused on encouraging the adoption of trusted identities through digital identity standards for federal agencies and internationally. - The supply chain that provides the information and operational technology (IT/OT) upon which we all depend has evolved into a complex, globally distributed, dynamic ecosystem enabling the development of highly refined, sophisticated, cost-effective, and reusable solutions. In FY 2017, we published a proposed process model providing a method to identify and prioritize IT/OT systems and components."}], "metadata": {"source": "2017 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Random Bit Generator (RBG) Constructions provide? (Part 4)"}, {"role": "assistant", "content": "nisms based on cryptographic algorithms. SP 800-90B, Recommendation for the Entropy Sources Used for Random Bit Generation , provides guidelines for the development and validation of entropy sources.\nThis document (SP 800-90C) specifies constructions for the implementation of random bit generators (RBGs) that include DRBG mechanisms as specified in SP 800-90A and that use entropy sources as specified in SP 80090B. Constructions for four classes of RBGs - namely, RBG1, RBG2, RBG3, and RBGC - are specified in this document. ## Keywords\n\ndeterministic random bit generator (DRBG); entropy; entropy source; random bit generator (RBG); randomness source; RBG1 construction; RBG2 construction; RBG3 construction; RBGC construction; subordinate DRBG (sub-DRBG). ## 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. ## Note to Readers\n\n1."}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Hardware Security Failure Scenarios_ Potential Hardware Weaknesses provide? (Part 4)"}, {"role": "assistant", "content": "osure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| 1. Introduction...................................................................................................................................6 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Background....................................................................................................................................7 |\n| 2.4.1. Hardware Design View .................................................................................................................8 |\n| 2.4.2. Research Concepts View ..............................................................................................................9 |\n| 2.4.3. Simplified Mapping of Published Vulnerabilities View.................................................................9 |\n| 3. Technical Approach......................................................................................................................10 |\n| 3.1.1."}], "metadata": {"source": "Hardware Security Failure Scenarios_ Potential Hardware Weaknesses", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\nications on the intranet servers from organization-managed hosts. An organization-managed host has a firewall, antivirus software, and a registry key indicating that it is managed by the organization.\n- „ When these same users log in from any other host such as a PC at a kiosk or in an Internet café, they should be able to access only a limited set of Web-based applications such as email and calendaring. The only condition for any host is that, if it is running a Windows operating system, it must be using one or more specific versions of Windows, with each specific version using the most current set of updates. - „ Executives have the same access rights as other employees, as well as access to the executive file share on the administrative server. The executives are only given this access from organizationmanaged hosts. - „ Members of the sales group have the same access rights as other employees. In addition, they should have full access to the sales database and the sales file share on the sales server when they are using their own organization-managed hosts; from other hosts, they can only access the sales file share on the sales folder. - „ Business partners should be able to access the extranet partner server from specified IP addresses only Monday to Friday between 9 a.m. and 5 p.m. Eastern time. - „ In addition to all other resources, network administrators should have access to a range of subnets that are assigned to network infrastructure devices. They only have this access if they are using their organization-managed hosts."}], "metadata": {"source": "Guide to SSL VPNs", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\n| DTR No: | DTR Description | Spec. Reference |\n|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|\n| | PKCS #1 v1.5 padding, the signatureAlgorithm field shall specify the rsaEncryption OID (as per Section 3.2 of [RFC3370]), and for ECDSA and RSA with PSS padding, the signatureAlgorithm shall be in accordance with Table 3-3 of [SP800-78]. | Security Object |\n| DTR-07.02.01.11 | The SignedData content type shall include the digital signature. | • [SP800-73], Part 1, Section 3.1.7 - Security Object |\n\n| DTR No: | DTR Description | Spec."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2003 Annual Report:\n\nWhat do a business's invoices have in common with email? If the business does both on the same computer, they may want to think more about computer security. Payroll, proprietary information, client or employee data - information is essential to a business's success. A computer failure or other system breach could cost a business anything from its reputation to its competitive advantage. The small business owner who recognizes the threat of computer crime and who takes steps to deter inappropriate activities is less likely to become a victim.\n\nThe vulnerability of any one small business may not seem significant to many other than the owner and employees. However, over 95 percent of all U.S. businesses are small and mediumsized businesses (SMBs) of 500 employees or less. Therefore a vulnerability common to a large percentage of all SMBs could pose a threat to the Nation's economic base. In the special arena of information security, vulnerable SMBs also run the risk of being compromised for use in crimes against governmental or large industrial systems upon which everyone relies. SMBs cannot always justify an extensive security program, or often a single full time expert. Nonetheless, they confront serious security challenges and must address security requirements based on identified needs.\n\nThe difficulty for these organizations is to identify needed/cost-effective security mechanisms and obtain training that is practical and cost effective. Such organizations also need to become more educated consumers in terms of security, so that their limited security resources are well applied to meet the most obvious and serious threats."}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories:\n\nManagement Training and Employment | Citizens] D.14 Health Access to Care Population Health Mgmt &Consumer Safety Health Care Administration Health Care Delivery Services Health Care Research and Practitioner Education D.15 Income Security General Retirement and Disability Unemployment Compensation Housing Assistance Food and Nutrition Assistance Survivor Compensation D.16 Law Enforcement Criminal Apprehension Criminal Investigation and Surveillance Citizen Protection Leadership Protection Property Protection Substance Control Crime Prevention Trade Law Enforcement D.17 Litigation &Judicial Activities Judicial Hearings Legal Defense Legal Investigation Legal Prosecution and Litigation Resolution Facilitation D.18 Federal Correctional Activities Criminal Incarceration Criminal Rehabilitation D.19 General Sciences &Innovation |"}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories", "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 Personnel Security?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy.\n\nThe criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.9 (NIST 3.1.9)?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\n3.1.9 | Insecure Images, Software and Firmware... 3.1.9 Insecure Images, Software and Firmware\n\nAdversaries may attempt to interfere with a storage device's software distribution, update, or installation process in order to introduce incorrect, outdated, or maliciously modified code (e."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "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 is CMMC practice AC.L2-3.1.11 (NIST 3.1.11)?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\n3.1.11 RSA Exponent\n\n| Test Assertion | TA-09."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "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 is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to A Formal Description of the SDNS Security Protocol at Layer 4 (SP4):\n\n3.2.1 SP4E External to Transport\n\nThe choice of modeling SP4E external to and independent from Transport introduces some limitations on the protection operations performed."}], "metadata": {"source": "A Formal Description of the SDNS Security Protocol at Layer 4 (SP4)", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\n| | Current Risk Analysis | Current Risk Analysis | Current Risk Analysis | | Likelihood before controls (%): 10% | Impact before controls ($): $1,500,000 | Exposure Rating before controls ($): $150,000 | | Planned Risk Response | Select all that apply: ☐ Accept ☐ Avoid | Transfer ☐ Mitigate | | Planned Risk Response Description | Add additional coverage to enterprise disaster recovery policy to ensure the direct losses caused by customer communication disruption from a covered event."}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Maintenance?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\nStandards and Technology, Interfaces for Personal Identity Verification , NIST Special Publication (SP) 800-73-4, May 2015 (includes updates as of 2/8/16). http://dx.doi.org/10.6028/NIST.SP.800-73-4.\n- [SP800-78] National Institute of Standards and Technology, Cryptographic Algorithms and Key Sizes for Personal Identity Verification , NIST Special Publication (SP) 800-78-4, May 2015. http://dx.doi.org/10.6028/NIST.SP.800-78-4."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\ney can hide software. By decoupling operating system dependencies from the host system, a container image may contain unknown vulnerable or insecure software, which poses a software supply chain risk.\nAdditionally, container contents may not be observable by some security auditing tools. In a well-managed HPC system, most software has already been installed as a baseline system environment. The applications developed using native libraries often run faster than a container. Hence, training users to develop programs in the HPC programming environment is one way to reduce exposure to container vulnerabilities. Additionally, many container ecosystems include the ability to attest that a container and its dependencies are supplied by a trusted provider, and there are tools (e.g., Qualys [49], Anchore [50], etc.) designed to audit container contents that provide supply chain and software audit management for HPC applications. Containers, container runtimes, and container orchestrators all increase the security attack surface for HPC systems, but carefully implemented container environments may potentially improve the overall security posture. Vulnerable or poorly configured container runtimes or container orchestrators can lead to exploitable environments and, in some cases, even privilege"}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\n3.2.6 Physical Security of the Cybersecurity Policy."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Workforce Framework for Cybersecurity (NICE Framework):\n\n| Purpose and Applicability................................................................................\n3 |\n| | 1.3 | Audience......................................................................................................... 3 |\n| | 1.4 | Organization of this Publication ...................................................................... 3 |\n| 2 | NICE Framework Building Blocks ........................................................................4 | NICE Framework Building Blocks ........................................................................4 |\n| | 2.1 | Task Statements............................................................................................."}], "metadata": {"source": "Workforce Framework for Cybersecurity (NICE Framework)", "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 AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\n3.1.1 Verify presence mmetric digital signature of CMS SignedData asy\n\n| Purpose | Con EFF_SIGNATURE_BLOCK is implemented as a firms that the CB SignedData type and is encoded as a Cryptographic Message Syntax external digital signature as defined in RFC 3852 |\n|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Reference(s) | 1. 3.1.10 Verify ne distinguished name\n\n| Purpose | C i e pivSigner- D t certifi at signed the biometrics. 3.1.11 Verify FASC-N\n\n| Purpose | Confirms that the signedAttrs of the SignerInfo includes the pivFASC-N attribute whose value matches the value of the FASC-N in the CHUID of the PIV card."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Metrics and Methodology for Hardware Security Constructs:\n\nThis document builds on that analysis to introduce a comprehensive methodology for analyzing various attack strategies that exploit vulnerabilities. The approach quantifies the sensitivity of hardware weaknesses by measuring the number of attack methodologies that can exploit them. An additional metric assesses the threat level of potential attacks based on the number of weaknesses they can target. Designed to be scalable and adaptable, this methodology can evolve with emerging attack patterns and hardware vulnerabilities to support the development of more secure future hardware designs while aiding in the identification and mitigation of vulnerabilities in existing systems.\n\nGiven the evolving nature of hardware security, new weaknesses and attack strategies will inevitably emerge. This work emphasizes the importance of continuously updating and expanding the analysis, and the methodology's robust design allows for seamless modifications. While this work focuses on hardware weaknesses, the methodology is applicable to all identified vulnerabilities, including those that may arise in the future. As such, the findings contribute to a growing body of knowledge to help mitigate existing vulnerabilities and guide the development of more secure hardware architectures. Ongoing research will be crucial in supporting decision-making and design considerations for security-resilient hardware."}], "metadata": {"source": "Metrics and Methodology for Hardware Security Constructs", "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 Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop provide? (Part 5)"}, {"role": "assistant", "content": "1.2 Background For The Federal | Profile...............................................................\n1 |\n| | 1.3 About the IoT Federal Profile Virtual | Workshop.............................................. 2 |\n| 2 Event Summary and Key Takeaways ...................................................................4 | 2 Event Summary and Key Takeaways ...................................................................4 | 2 Event Summary and Key Takeaways ...................................................................4 |\n| | 2.1 Keynote: Federal Chief Information Security | Officer....................................... 4 |\n| 2.2 | Summary and Takeaways from Panel | Sessions............................................."}], "metadata": {"source": "Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nDEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION ..................................................................................\n7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ..................................................................................... 32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................"}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\nCloud-native applications have evolved into a standardized architecture consisting of multiple loosely coupled components called microservices (often typically implemented as containers) that are supported by an infrastructure for providing application services, such as service mesh. Both of these components are usually hosted on a container orchestration and resource management platform. In this architecture, the entire set of source code involved in the application environment can be divided into five code types: 1) application code (which embodies the application logic), 2) application services code (for services such as session establishment, network connection, etc.), 3) infrastructure as code (for provisioning and configuring computing, networking, and storage resources), 4) policy as code (for defining runtime policies such as zero trust expressed as a declarative code), 5) and observability as code (for the continuous monitoring of an application runtime state). Due to security, business competitiveness, and the inherent structure of loosely coupled application components, this class of applications needs a different development, deployment, and runtime paradigm. DevSecOps (consisting of acronyms for Development, Security, and Operations, respectively) has been found to be a facilitating paradigm for these applications with primitives such as continuous integration, continuous delivery, and continuous deployment (CI/CD) pipelines. These pipelines are workflows for taking the developer's source code through various stages, such as building, testing, packaging, deployment, and operations supported by automated tools with feedback mechanisms. The objective of this document is to provide guidance for the implementation of DevSecOps primitives for cloud-native applications with the architecture and code types described above. The benefits of this approach for high security assurance and for enabling continuous authority to operate (C-ATO) are also discussed."}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Computer Security Division 2005 Annual Report:\n\nmmunity. - Methods for assessing effectiveness of security requirements - SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems (first public draft issued July 2005).\n- Procedures for capturing results of security requirement assessments and results of security program assessments - SP 800-26 Revision 1, Guide for Information Security Program Assessments and System Reporting Form (first public draft issued August 2005). - Bring the security planning process up to date with key standards and guidelines developed by NIST - SP 800-18 Revision 1, Guide for Developing Security Plans for Federal Information Systems (first public draft issued August 2005). - Provide assistance to Agencies and private sector - Conduct ongoing, substantial reimbursable and non-reimbursable assistance support, including many outreach efforts such as the Federal Information Systems Security Educators' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSM Forum), the Small Business Corner, and the Program Review for Information Security Management Assistance (PRISMA). - Evaluate security policies and technologies from the private sector and national security systems for potential Federal agency use - Host a growing repository of Federal agency security practices, public/private security practices, and security configuration checklists for IT products. In conjunction with the Government of Canada's Communications Security Establishment, CSD leads the Cryptographic Module Validation Program (CMVP). The Common Criteria Evaluation and Validation Scheme (CCEVS) and CMVP facilitate security testing of IT products usable by the Federal government. - Solicit recommendations of the Information Security and Privacy Advisory Board on draft standards and guidelines - Solicit recommendations of the Board regularly at quarterly meetings."}], "metadata": {"source": "Computer Security Division 2005 Annual Report", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Information Technology Security Services:\n\n| 5.2.3 | Testing..........................................................................................................5-8 | | | 5.2.4 | Training ........................................................................................................5-9 | | 5.3 | Technical Security Services...................................................................................5-11 | Technical Security Services...................................................................................5-11 | | | 5.3.1 | Firewalls .....................................................................................................5-11 | | | 5.3.2 | Intrusion Detection .....................................................................................5-11 | | | 5.3.3 | Public Key Infrastructure ............................................................................5-12 | | Appendix A-REFERENCES.................................................................................................A-1 | Appendix A-REFERENCES.................................................................................................A-1 | Appendix A-REFERENCES.................................................................................................A-1 | | Appendix B-ACRONYM LIST..............................................................................................B-1 | Appendix B-ACRONYM LIST..............................................................................................B-1 | Appendix B-ACRONYM LIST..............................................................................................B-1 | | Appendix C-SERVICE AGREEMENT OUTLINE................................................................"}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\n3.4.2 | Synchronization... 3.4.2 Synchronization\n\nSynchronization of attribute transmission sequences between access control functions must be coordinated based on the sequence of the access control system's processing scheme or protocol such that the updates of attributes and their values will not result in faulty access control decisions."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Configuration Management?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\n| 1. | There is broad support for expanding the discussion of IoT products in NIST IR 8259 to make products more central to the IoT cybersecurity baseline and allow further exploration of the cybersecurity considerations of other IoT product components beyond the device. |\n|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Many cybersecurity challenges are aggravated by the limited visibility each role in the IoT ecosystem (e.g., manufacturer, integrator, customer) has into the cybersecurity of the whole system . |\n| 3 | Performing risk analysis for IoT products remains a challenge due to the potential for unintended use or unexpected environments of use. |\n| 4 | In understanding the magnitude of a risk, it is important to understand the scale of the potential impact from a threat. |\n| 5 | Communicating effectively throughout IoT pre-market and post-market activities involves bridging gaps between manufacturer knowledge and customer ability to use the information. |\n| 6 | Transparency and traceability are foundational to maintaining product cybersecurity throughout the IoT product lifecycle. |\n| 7 | Discussions throughout the workshop highlighted challenges in IoT product lifecycle management emphasizing IoT product risks, vulnerabilities, and evolving ecosystem demands. |"}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "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 Cybersecurity of Genomic Data provide? (Part 5)"}, {"role": "assistant", "content": "## Table of Contents | Introduction....................................................................................................................1 | Introduction....................................................................................................................1 | Introduction....................................................................................................................1 | |-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | | Cybersecurity and Privacy Concerns.........................................................................1 | | | | Document Scope and Goals......................................................................................2 | | | Background....................................................................................................................3 | Background....................................................................................................................3 | Background....................................................................................................................3 | | | Genomic Information Lifecycle | ..................................................................................3 | | | Next Generation Sequencing.....................................................................................4 | | | | Variant Calling | ...........................................................................................................4 | | | Genome Editing.........................................................................................................5 | | | | Direct-to-Consumer Testing.......................................................................................5 | | | | The Characteristics of Genomic Data........................................................................6 | | | | Balance Between Benefits and Risks for Uses of Genomic Information | ...................7 | | Challenges and Concerns Associated with Handling Genomic Information...........9 | Challenges and Concerns Associated with Handling Genomic Information...........9 | Challenges and Concerns Associated with Handling Genomic Information...........9 | | | Potential National Security Concerns ........................................................................9 | | | 3.2."}], "metadata": {"source": "Cybersecurity of Genomic Data", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Proceedings of the Workshop of the Federal Criteria for Information Technology Security:\n\nAlthough networking issues had been declared out of bounds during the opening plenary session, there was general consensus that plain text nansmission of passwords was too important a vulnerability to ignore. Networic monitoring hardware and software makes it very easy for passwords to be compromised. Users without private offices were identified as being vulnerable to password compromise.\n\nAvailability covers much more than security; availability is not a security service, according to GOSIP. Denial of service is only one type of threat Resource allocation is a duty of the system administrator. Fault management is not security management The TCB should be expanded to provide these services. The components of availability are containment, fault tolerance, robustness, and recovery. Customers take a holistic view; so should the FC.\n\nSentiment was expressed that many of the components in Chapter 4 of the Federal Criteria have been randomly put into a hierarchy. The structure may be related to the policy that a particular system implements and/or the type of threat addressed. Since the relative importance of threats will vary among environments, a hierarchy is not appropriate."}], "metadata": {"source": "Proceedings of the Workshop of the Federal Criteria for Information Technology Security", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.1.4. 3.1.4."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Annual Report 2018_ NIST_ITL Cybersecurity Program:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\nIn Fiscal Year 2018, we received and worked on new cybersecurity-related assignments from Congress and the President. Those have led us to focus our attention on assisting small businesses, forging practical solutions to address security concerns raised by the Internet of Things, and updating our guidance on risk management and security controls for federal agencies and others. We also launched major new initiatives, including the development of a voluntary framework for privacy risk management, standards for\n\nOne thing has remained constant over the past decade: our commitment to cultivating trust in information and the technology that drives the development and handling of that information. This annual report focuses on some of NIST's most noteworthy cybersecurity achievements in 2018 and offers insights into our current priorities and strategies. For a more complete review of our work, check out our primary cybersecurity website. 2"}], "metadata": {"source": "Annual Report 2018_ NIST_ITL Cybersecurity Program", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Information Security Guide for Government Executives:\n\nIt is the vehicle for disseminating security information that the workforce, including managers, needs to do their jobs. These programs will ensure that personnel at all levels of the organization understand their information security responsibilities to properly use and protect the information resources entrusted to them. Awareness is a blended solution of activities that promotes security, establishes accountability, and informs the workforce of security news. Training strives to produce relevant and needed security knowledge and skills within the workforce. Training supports competency development and helps personnel understand and learn how to perform their security role. Education integrates all of the security skills and competencies of the various functional specialties into a common body of knowledge and adds a multidisciplinary study of concepts, issues, and principles (technological and social). NIST SP 800-50, Building an Information Technology Security Awareness and Training Program |\n| Information Security Governance | The purpose of information security governance is to ensure that agencies are proactively implementing appropriate information security controls to support their mission in a cost-effective manner, while managing evolving information security risks. Information security governance has its own set of requirements, challenges, activities, and types of possible structures. Information security governance also has a defining role in identifying key information security roles and responsibilities, and it influences information security policy development and oversight and ongoing monitoring activities."}], "metadata": {"source": "Information Security Guide for Government Executives", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\nassessment; assessment method; assessment object; assessment procedure; assurance; enhanced security requirement; enhanced security requirement assessment; Controlled Unclassified Information; coverage; CUI Registry; depth; Executive Order 13556; FISMA; NIST Special Publication 800-53; NIST Special Publication 800-53A; NIST Special Publication 800-171; NIST Special Publication 800-172; NIST Special Publication 800-172A; nonfederal organization; nonfederal system; security assessment; security control. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity:\n\nCore areas of cybersecurity standardization include: cryptographic techniques; cyber incident management; identity and access management; IT system security evaluation; information security management systems; network security; security automation and continuous monitoring; supply chain risk management; software | Core Areas of Cybersecurity Standardization | Examples of Relevant SDOs | Examples of Some Key Applications | Examples of Some Key Applications | Examples of Some Key Applications | Examples of Some Key Applications | Examples of Some Key Applications | Examples of Some Key Applications | |-----------------------------------------------|--------------------------------------------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------|-------------------------------------| | Core Areas of Cybersecurity Standardization | Examples of Relevant SDOs | Cloud Computing | Emergency Management | Industrial Control Systems | Health IT | Smart Grid | Voting | | Cryptographic Techniques | IEEE ISO TC 68 ISO/IEC JTC 1 W3C | Standards Mostly Available | Some Standards Available | Some Standards Available | Some Standards Available | Some Standards Available | Some Standards Available | | Cyber Incident Management | ISO/IEC JTC 1 ITU-T PCI | Some Standards Available | New Standards Needed | Some Standards Available | Some Standards Available | Some Standards Available | New Standards Needed | | Identity and Access Management | FIDO Alliance IETF; OASIS OIDF ISO/IEC JTC 1"}], "metadata": {"source": "Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity", "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 Communications Protection?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Federal Information and Information Systems:\n\nstems; and (ii) employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational information systems.\nNATIONAL SECURITY SYSTEM: Any information system (including any telecommunications system) used or operated by an agency or by a contractor of an agency, or other organization on behalf of an agency- (i) the function, operation, or use of which involves intelligence activities; involves cryptologic activities related to national security; involves command and control of military forces; involves equipment that is an integral part of a weapon or weapons system; or is critical to the direct fulfillment of military or intelligence missions (excluding a system that is to be used for routine administrative and business applications, for example, payroll, finance, logistics, and personnel management applications); or (ii) is protected at all times by procedures established for information that have been specifically authorized under criteria established by an Executive Order or an Act of Congress to be kept classified in the interest of national defense or foreign policy. [44 U.S.C., SEC. 3542]"}], "metadata": {"source": "Minimum Security Requirements for Federal Information and 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 Personnel Security?"}, {"role": "assistant", "content": "According to Information System Security Best Practices for UOCAVA-Supporting Systems:\n\nJurisdictions that want to be able to validate signed email from military personnel need to install the trust anchor for the US Department of Defense Root CA. This certificate can currently be found at\n\nSome of the more intensive training programs can lead to certification for the trainee. There are a variety of certifications for security personnel from various independent organizations, and each certification has its own level of value and appropriateness for particular tasks. Some of the many types of security certifications include proof of skills such as:"}], "metadata": {"source": "Information System Security Best Practices for UOCAVA-Supporting Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Integrating Forensic Techniques into Incident Response:\n\nes ............................................................................... | 8. Using Data from Multiple Sources ...............................................................................\n| 8-1 |\n| 8.1 | Suspected Network Service Worm | 8-1 |\n| 8.2 | Threatening E-mail................................................................................................ | Infection.......................................................... 8-3 |\n| 8.3 | Recommendations | ................................................................................................"}], "metadata": {"source": "Guide to Integrating Forensic Techniques into Incident Response", "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 Guide to Integrating Forensic Techniques into Incident Response:\n\nmay be limited or missing. If the software was configured to forward copies of its logs to centralized log servers, then queries to those servers may provide some information. - ! Antivirus Software.\nBecause the threat reached the server and successfully breached it, it is unlikely that network or host-based antivirus software contains any record of the threat. If antivirus software had detected the worm, it should have stopped it. However, it is possible that the antivirus software saw the worm but somehow failed to stop it, or that the antivirus software was updated since the infection with new signatures that can recognize the worm. The incident handler can also scan the server for worms using a current version of antivirus software from a forensic toolkit. - ! Application Logs. If the worm used a common application protocol, such as HTTP or SMTP, information regarding it might be recorded in several places, such as application server logs, proxy servers, and application-specific security controls. Less common application protocols probably have information only in the application server logs. Application logs record extensive details on the application-specific characteristics of the activity, and are particularly helpful at identifying attack characteristics from less common applications."}], "metadata": {"source": "Guide to Integrating Forensic Techniques into Incident Response", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-55v2\n\n## Measurement Guide for Information Security\n\nVolume 2 - Developing an Information Security Measurement Program\n\nKatherine Schroeder Hung Trinh Victoria Yan Pillitteri\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-55v2\n\n\n\n## NIST Special Publication 800 NIST SP 800-55v2\n\n## Measurement Guide for Information Security\n\nVolume 2 - Developing an Information Security Measurement Program\n\nKatherine Schroeder Hung Trinh\n\nVictoria Yan Pillitteri\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-55v2\n\nDecember 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. accordance with its assigned statutory responsibilities. The information in this publication, including concepts and\n\nThere may be references in this publication to other publications currently under development by NIST in 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": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Personnel Security?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0:\n\nmplemented outside of the information technology with an example counter-measure being physical protections such as locked offices and guarded buildings and an example attack being social engineering.\n| Name | Policy | Discussion |\n|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| P.PHYSICAL | The processing resources of the TOE that must be physically protected in order to ensure that security objectives are met will be located within controlled access facilities that mitigate unauthorized, physical access. | A TOE will not be able to meet its security requirements unless at least a minimum degree of physical security is provided."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "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 Managing Information Security Risk_ Organization, Mission, and Information System View:\n\non-wide. Those same vulnerabilities may trigger changes to the enterprise architecture and embedded information security architecture or may require an adjustment to the organizational risk tolerance.\nSection 2.5 provides a more detailed description of the specific activities associated with Tier 3."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile:\n\n-  A method to identify opportunities for improving the current cybersecurity posture of the manufacturing system -  An evaluation of their ability to operate the control environment at their acceptable risk level -  A standardized approach to preparing the cybersecurity plan for ongoing assurance of the manufacturing system's security | Function | Category | Subcategory | Manufacturing Profile | Reference | |------------|-------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| | IDENTIFY | Governance (ID.GV) | ID.GV-4 | Low, Moderate and High Develop a comprehensive strategy to manage risk to manufacturing operations."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.5 (NIST 3.6.5)?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n3.6.5 | The attribute value is an X."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "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 additional guidance does A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data provide? (Part 3)"}, {"role": "assistant", "content": "e key software in that virtualized infrastructure. However, hypervisors are large pieces of software with several thousand lines of code and are therefore known to have vulnerabilities.\nHence a capability to perform forensic analysis to detect, reconstruct and prevent attacks based on recent vulnerabilities on an ongoing basis is a critical requirement in cloud environments. The purpose of this document is to develop a methodology to enable this forensic analysis. Two open-source hypervisors-Xen and Kernel-based Virtual Machine (KVM)-were chosen as platforms to illustrate the methodology, and the source for vulnerability data is the National Institute of Standards and Technology's National Vulnerability Database (NIST-NVD). The vulnerabilities were classified in terms of hypervisor functionality, attack type, and attack source. Based on the relative distribution of vulnerabilities in a hypervisor functionality, two sample attacks were launched to exploit vulnerabilities in the target hypervisor functionality, and the associated system calls were logged. The gaps in evidence data that is required for fully detecting and reconstructing those attacks are identified and techniques required to gather missing evidence are incorporated during subsequent attack runs. This is intended to be an iterative process. ## Keywords\n\ncloud computing; forensic analysis; hypervisors; Kernel-based Virtual Machine (KVM); vulnerabilities; Xen\n\n## Acknowledgments\n\nThe authors thank Ms. Isabel Van Wyk for her valuable editorial review. ## Audience\n\nThe target audience for this document includes security staff and Chief Information Security Officers (CISO) in virtualized infrastructures used for enterprise computing needs or for offering cloud services. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations."}], "metadata": {"source": "A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Obtaining Assurances for Digital Signature Applications:\n\n1. a, b and c should be selected with regard to the judgments to be made about the validity of the digital signatures processed. Consideration should also be given to the ease (or difficulty) of (repeatedly) using a given method to explicitly obtain assurance of possession.\n2. A value of d shall be selected such that d is less than one half the minimum of a and b (i.e., d < ½ min ( a, b )). An interval of length d must allow sufficient time for the acquisition of time t 1, the actions required to provide/obtain assurance, and the\n\nacquisition of time t 2. In particular, expected transmission times between various parties who must exchange information should be considered when selecting d ."}], "metadata": {"source": "Recommendation for Obtaining Assurances for Digital Signature Applications", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Computer Security Division 2014 Annual Report:\n\n|\n| INTRODUCTION TO CSD'S FIVE GROUPS.....................................................................................................................................\n| 3 |\n| Cryptographic Technology Group (CTG)........................................................................................................................................................4 | |\n| Security Components and Mechanisms Group (SCMG).............................................................................................................................4 | |\n| Secure Systems and Applications Group (SSAG)..........................................................................................................................................5 | |\n| Security Outreach and Integration Group (SOIG)........................................................................................................................................"}], "metadata": {"source": "Computer Security Division 2014 Annual Report", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Research Report_ User Perceptions of Smart Home Privacy and Security:\n\n3.2.5 | Household Profiling | 16 |\n| | 3. 3.2.5 Household Profiling\n\nOne of the concerns mentioned in the privacy context was the profiling of household members, including their pattern of life, what kinds of things they like, approximate ages of household members, and 'the literal movements of our family,."}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Platform Firmware Resiliency Guidelines:\n\n3.5.3 | Secure Local Update... 3.5.3 Secure Local Update\n\nWhile this document recommends firmware updates be done through an authenticated update mechanism as described in Section 3. 3.5.3."}], "metadata": {"source": "Platform Firmware Resiliency Guidelines", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\n## 5.1 Integrity Techniques\n\n- Integrity Techniques - Specify the approved integrity techniques or EDC [error detection code] employed\n\n- Initiate on Demand - Specify how the operator can initiate the integrity test on demand"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines on Active Content and Mobile Code:\n\nine environment for systems and applications to execute. Risky functions, such as Web browsing, may be confined to a virtual machine environment designated and configured exclusively for that purpose.\nThis presumes that the virtualization software controlling the various virtual machine environments has adequate security [Gar07]. Should a virtual machine environment be compromised or become suspect, it can be replaced with the original version. Virtual machine technology is improving constantly. New versions of mainstream OSs are being designed with virtualization in mind and new x86 64-bit processors provide hardware-level support for virtualization."}], "metadata": {"source": "Guidelines on Active Content and Mobile Code", "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 The NIST Cybersecurity Framework (CSF) 2.0:\n\n- improvement opportunities for the organization's policies, plans, processes, procedures, and practices that support cybersecurity risk management to inform efforts under all six Functions. - PROTECT (PR) -Safeguards to manage the organization's cybersecurity risks are used. Once assets and risks are identified and prioritized, PROTECT supports the ability to secure those assets to prevent or lower the likelihood and impact of adverse cybersecurity events, as well as to increase the likelihood and impact of taking advantage of opportunities. Outcomes covered by this Function include identity management, authentication, and access control; awareness and training; data security; platform security (i.e., securing the hardware, software, and services of physical and virtual platforms); and the resilience of technology infrastructure. - DETECT (DE) -Possible cybersecurity attacks and compromises are found and analyzed. DETECT enables the timely discovery and analysis of anomalies, indicators of compromise, and other potentially adverse events that may indicate that cybersecurity attacks and incidents are occurring. This Function supports successful incident response and recovery activities. - RESPOND (RS) -Actions regarding a detected cybersecurity incident are taken. RESPOND supports the ability to contain the effects of cybersecurity incidents. Outcomes within this Function cover incident management, analysis, mitigation, reporting, and communication. - RECOVER (RC) -Assets and operations affected by a cybersecurity incident are restored. RECOVER supports the timely restoration of normal operations to reduce the effects of cybersecurity incidents and enable appropriate communication during recovery efforts. Figure 2 shows the CSF Functions as a wheel because all of the Functions relate to one another. For example, an organization will categorize assets under IDENTIFY and take steps to secure those assets under PROTECT."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.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 does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings:\n\nigned by a trusted CA provides a mechanism that may be used for enabling the credential to be verified and revoked. |\n| Certificate Authority (CA) | Issues and signs certificates as needed.\n| Supports (integral to) PR.AC- 6: Identities are proofed and bound to credentials and asserted in interactions | If the device credential is an X.509 certificate (e.g., an IDevID) that is signed by a CA, this certificate binds the device's credential to the device's identity. |\n| Application- Layer Onboarding Service | After the device connects to the network, this component interacts with the device using… | Is Supported by (precedes) ID.AM-2: Software platforms and applications within the organization are inventoried | In some application-layer onboarding mechanisms, the IoT device must be prepared for application-layer onboarding during the factory provisioning process. In these cases, the… |"}], "metadata": {"source": "Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings", "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 Module-Lattice-Based Digital Signature Standard provide? (Part 3)"}, {"role": "assistant", "content": "user who possesses the private key can generate a signature that can be verified by the corresponding public key. The digital signature is provided to the intended verifier along with the signed data.\nThe verifying entity verifies the signature by using the claimed signatory's public key. Similar procedures may be used to generate and verify signatures for both stored and transmitted data. This standard specifies several parameter sets for ML-DSA that are approved for use. Additional parameter sets may be specified and approved in future NIST Special Publications. 4. Approving Authority. Secretary of Commerce. 5. Maintenance Agency. Department of Commerce, National Institute of Standards and Technology, Information Technology Laboratory (ITL). 6. Applicability. This standard is applicable to all federal departments and agencies for the protection of sensitive unclassified information that is not subject to section 2315 of Title 10, United States Code, or section 3502 (2) of Title 44, United States Code. Either this standard, FIPS 205, FIPS 186-5, or NIST Special Publication 800-208 shall be used in designing and implementing public-key-based signature systems that federal departments and agencies operate or that are operated for them under contract. In the future, additional digital signature schemes may be specified and approved in FIPS or NIST Special Publications. The adoption and use of this standard are available to private and commercial organizations. 7. Applications. A digital signature algorithm allows an entity to authenticate the integrity of signed data and the identity of the signatory. The recipient of a signed message can use a digital signature as evidence in demonstrating to a third party that the signature was, in fact, generated by the claimed signatory. This is known as non-repudiation since the signatory cannot easily repudiate the signature at a later time."}], "metadata": {"source": "Module-Lattice-Based Digital Signature Standard", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n' OS fingerprints and application error messages. Some products can also prevent sensitive information such as social security numbers and credit card numbers from being displayed on Web server pages.\nSome host-based IDPSs offer additional capabilities related to intrusion detection and prevention, such as enforcing restrictions on the use of removable media, detecting the activation or use of audiovisual devices, automatically hardening hosts on an ongoing basis, monitoring the status of running processes and restarting failed ones, and performing network traffic sanitization."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Recommendation for Obtaining Assurances for Digital Signature Applications:\n\n3.2.1). 3.2.1 Assigning the assurance\\_time for the Regeneration of Keys\n\nSection 6. 3.2.1, then the initial assurance level should be assigned as follows:\n\n- a."}], "metadata": {"source": "Recommendation for Obtaining Assurances for Digital Signature Applications", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Vetting the Security of Mobile Applications:\n\nut notice, performance impact (e.g., battery), etc. prior to allowing them to be hosted in their app market. The level and type of reviews conducted are opaque to consumers and the federal government.\nFurthermore, these app markets serve a global customer base that numbers in the billions and their reviews of apps are consumer- and brand-focused. Enterprise organizations  federal agencies, regulated industries, other non-governmental organizations  that plan to use consumer apps for their business will need to make risk-based decisions for app acquisition based on their own security, privacy and policy requirements and risk tolerance."}], "metadata": {"source": "Vetting the Security of Mobile Applications", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.:\n\nContractual requirements are the principal mechanism for setting a baseline foundation to manage cyber supply chain risks. During the onboarding process, new suppliers are subject to a detailed security assessment. These assessments are based on specific security council priorities, the NIST Cybersecurity Framework (NIST CSF) v , International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 28001 vi , and other standards and best practices. The assessment ensures that all supplier employees receive security training and that the assessment team inspects the supplier's factory and warehouse facilities to confirm that unauthorized personnel cannot access Palo Alto Networks components. Suppliers must also demonstrate conformance to relevant requirements, such as FIPS, CPA, and the U.S. Customs and Border Protection's (CBP) Customs-Trade Partnership Against Terrorism (CTPAT) program. In addition to supplier onboarding and annual security assessments, suppliers are contractually obligated to disclose component vulnerabilities, data loss, and security incidents to Palo Alto Networks. This process provides the SCRC team a more complete view of the supplier's cybersecurity posture, including real-time alerts of a potential incident. Strategic suppliers must use Palo Alto Networks' cybersecurity products to provide confidence in the supplier's cyber incident detection and response capabilities. Palo Alto Networks ensures consistent quality management and product security with a wide range of handling policies. All materials related to the production of Palo Alto Networks products must be stored in facilities with strict access controls and 24/7 physical and electronic monitoring. The CM is required to perform complete background, reference, and employment history checks for every candidate before they may access and work on Palo Alto Networks products."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "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 AU.L2-3.3.6 (NIST 3.3.6)?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n3.3.6, 3. 3.3.6, 3."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "nist_control": "3.3.6", "cmmc_practice_id": "AU.L2-3.3.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Storage Encryption Technologies for End User Devices:\n\n| Introduction ......................................................................................................................1-1 | Introduction ......................................................................................................................1-1 | Introduction ......................................................................................................................1-1 | | | 1.1 | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope .................................................................................................1-1 | | | | 1.3 | Audience..................................................................................................................1-1 | | | | 1.4 | Document Structure.................................................................................................1-1 | | | 2."}], "metadata": {"source": "Guide to Storage Encryption Technologies for End User 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 Maintenance?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThe new format for assessment procedures introduced in Special Publication (SP) 800-53A Revision 4, is\nfurther improved in this revision (SP 800-53A Revision 5). The format continues to reflect the\ndecomposition of assessment objectives into more granular determination statements wherever possible,\nthus providing the capability to identify and assess specific parts of security and privacy controls. Updates\nto SP 800-53A Revision 5:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ..............................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n| 2.10.3 Derived PIV Credential Reissuance and Update Requirements . . . . . . . . . . . . . . . . . | . 27 |\n|----------------------------------------------------------------------------------------------------------------------------|--------|\n| 2.11 PIV Privacy Requirements . . . . | . 28 |\n| 3. PIV System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . | . 30 |\n| 3.1 Functional Components . . . . . . . . . . . . . . . . . . . . . . . | . 30 |\n| 3.1.1 PIV Front-End Subsystem . . . . . . . . . . . . . . . . . . | . 31 |\n| 3.1.2 PIV Issuance and Management Subsystem . . . . . . . . . . . . . . . . . | . 32 |\n| 3.1.3 PIV Relying Subsystem . . . . . . . . . . . | . 34 |\n| 3.2 PIV Card Lifecycle Activities . . . . . . . . . . . . . . . . . . . . | . 35 |\n| 3.3 Connections Between System Components . . . . . . . . . . . . . | . 37 |\n| 4. PIV Front-End Subsystem . . . . . . . . . . . . . . . . . . . . . . . | . 39 |\n| 4.1 PIV Card Physical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . | . 39 |\n| 4.1.1 Printed Material . . . . . . . . . . . . . . . . | . 39 |\n| 4.1.2 Tamper-proofing and Resistance . . . . . . . . . . . . . . | . 39 |\n| 4.1.3 Physical Characteristics and Durability . . . . . . . . . . . . . | . 40 |\n| 4.1.4 Visual Card Topography . . . . . . . . . . . . . . . . . . . | . 42 |\n| 4.1.5 Color Representation . . . . . . . . . . . . . . . . . | . 58 |\n| 4.2 PIV Card Logical Characteristics . . . . . . . . . . . . . . . . . . . . . | . 58 . |\n| 4.2.1 Cardholder Unique Identifier . . . . . . . . . . . . . | 60 |\n| 4.2.2 Cryptographic Specifications . . . . . . . . . . . . . . . . | . 61 |\n| 4.2.3 Biometric Data Specifications . . . . . . . . . . . . . . . . . . . | . 65 |\n| 4.2.4 PIV Unique Identifiers . . . . . . . . . . . . . . . . . . . . . . | . 67 |\n| 4.3 PIV Card Activation . . . . . . . . . . . . . . . . . . | . 68 |\n| 4.3.1 Activation by Cardholder . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "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 Maintenance?"}, {"role": "assistant", "content": "According to Guidelines on Electronic Mail Security:\n\n| 5.3 Checklist for Securing the Mail Server Operating System.......................................5-7 | 5.3 Checklist for Securing the Mail Server Operating System.......................................5-7 | | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| | Securing Mail | Servers and | Content................................................................................6-1 | | 6.1 Hardening the Mail Server Application.....................................................................6-1 | 6.1 Hardening the Mail Server Application.....................................................................6-1 | | | 6.1.1 | Securely Installing the Mail Server | ...............................................................6-1 | | 6.1.2 | Configuring Operating System and Mail Server Access Controls | ................6-1 | | | Protecting Email from Malware................................................................................6-3 | | | 6.2 6.2.1 | Malware Scanning........................................................................................6-5 | | | 6.2.2 | Content Filtering | ...........................................................................................6-9 | | 6.2.3 | User Awareness | .........................................................................................6-12 | | 6.3 | Blocking Spam-Sending Servers | ...........................................................................6-13 | | 6.4 | Authenticated Mail Relay | .......................................................................................6-14 | | 6.5 | Secure Access.......................................................................................................6-14 | | | 6.6 | Enabling Web Access............................................................................................6-15 | | | 6.7 | Checklist for Securing Mail Servers and Content | ..................................................6-16 | | Implementing a Secure Network Infrastructure ............................................................7-1 | Implementing a Secure Network Infrastructure ............................................................7-1 | | | 7.1 | Network Composition and Structure | ........................................................................7-1 | | | 7.1.1 Inadvisable Network Layout | .........................................................................7-1 | | 7.1.2 | Demilitarized Zone........................................................................................7-1 | | | | 7.1.4 Management Network | ..................................................................................7-5"}], "metadata": {"source": "Guidelines on Electronic Mail Security", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Platform Firmware Resiliency Guidelines:\n\n| Introduction...........................................................................................................................\n1 | Introduction..........................................................................................................................."}], "metadata": {"source": "Platform Firmware Resiliency Guidelines", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Block Cipher Modes of Operation_ Methods and Techniques:\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 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."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Methods and Techniques", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security Considerations for Remote Electronic UOCAVA Voting:\n\n.. 4 | 2 GENERAL ARCHITECTURE............................................................ 4 | 2 GENERAL ARCHITECTURE............................................................\n4 |\n| 2.1 | SYSTEM COMPONENTS | ....................................................................4 |\n| 2.2 | AUTHORIZED USERS.......................................................................7 | |\n| 2.3 | THREAT SOURCES..........................................................................8 | |\n| 3 OVERVIEW................................................................................ 12 | 3 OVERVIEW................................................................................ 12 | 3 OVERVIEW................................................................................ 12 |\n| 4 | CONFIDENTIALITY...................................................................."}], "metadata": {"source": "Security Considerations for Remote Electronic UOCAVA Voting", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to BIOS Protection Guidelines:\n\n| Introduction.......................................................................................................................1-1 | | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Authority ...................................................................................................................1-1 | | | 1.2 | Purpose and Scope..................................................................................................1-1 | | | 1.3 | Audience ..................................................................................................................1-2 | | | 1.4 | Document Structure .................................................................................................1-2 | | 2."}], "metadata": {"source": "BIOS Protection 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 guidance does Assessing Security and Privacy Controls in Information Systems and Organizations provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-53A\nRevision 5\n\nAssessing Security and Privacy Controls in\nInformation Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\n\f NIST Special Publication 800-53A\nRevision 5\n\n Assessing Security and Privacy Controls\nin Information Systems and\nOrganizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53Ar5\n\nJanuary 2022\n\nNational Institute of Standards and Technology\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce\nfor Standards and Technology & Director, National Institute of Standards and Technology\n\nU.S. Department of Commerce\nGina M. Raimondo, Secretary\n\n\fAuthority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the\nFederal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq., Public Law\n(P.L.) 113-283. NIST is responsible for developing information security standards and guidelines,\nincluding minimum requirements for federal information systems. Such information security\nstandards and guidelines shall not apply to national security systems without the express\napproval of the appropriate federal officials exercising policy authority over such systems. This\nguideline is consistent with the requirements of the Office of Management and Budget (OMB)\nCircular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made\nmandatory and binding on federal agencies by the Secretary of Commerce under statutory\nauthority. Nor should these guidelines be interpreted as altering or superseding the existing\nauthorities of the Secretary of Commerce, OMB Director, or any other federal official. This\npublication may be used by nongovernmental organizations on a voluntary basis and is not\nsubject to copyright in the United States."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Hardware Security Failure Scenarios_ Potential Hardware Weaknesses:\n\nWE-1196).............................................44 |\n| Fig.\n21.HWCWEs under the category Security Primitives and Cryptography Issues (CWE-1205).........45 |\n| Fig. 22. HWCWEcomplete graph with View-1003 pillar and class CWEs that are not in View-1194 highlighted ..........................................................................................................................46 |\n| Fig. 23. HWCWEcomplete graph with View-1003 base CWEs that overlap with View-1194 highlighted ........................................................................................................................................................48 |\n| Fig. 24. HWCWEcomplete graph with memory-related weaknesses highlighted ...............................49 |\n| Fig. 25. View-699 CWEs that overlap with View-1194 highlighted......................................................50 |\n| Fig. 26. The 12 CWEs in both View-1194 and View-699......................................................................52 |\n| Fig. 27. HWCWECategory Graph: Improper Access Control ..............................................................69 |"}], "metadata": {"source": "Hardware Security Failure Scenarios_ Potential Hardware Weaknesses", "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 Maintenance?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\nto apply significant compensating controls. 4. What are the physical, logical access, network, and other requirements of the IoT device and how do they relate to key device cybersecurity requirements?\nAn understanding of how the IoT device will interact with the digital and physical worlds is important to understanding whether the device should be used by the organization and, if so, the cybersecurity risks and corresponding mitigations that are practical, possible, and appropriate. For example, knowing the endpoints (both internet domains and local devices) the IoT device must connect to can help an organization ensure all connections the device will make (and the logical access via those endpoints) are acceptable within the organization's security policy. Physical requirements, such as the need to access the device for maintenance or diagnostics may conflict with how some devices are deployed (e.g., if they must be placed in an inaccessible location making physical maintenance difficult or impossible)."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.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 does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators:\n\nLet df be the derivation function specified in Section 10.3.2. When instantiation is performed using this method, a nonce is required, whereas using the method in Section 10.2.1.3.1 does not require a nonce, since full entropy is provided when using that method.\n\nLet df be the derivation function specified in Section 10.3.2.\n\nLet df be the derivation function specified in Section 10.3.2."}], "metadata": {"source": "Recommendation for Random Number Generation Using Deterministic Random Bit Generators", "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 Guidelines for the Secure Deployment of IPv6:\n\n| | 5.3.3 | Support for Multicast .................................................................................. | 5-8 |\n|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|\n| | 5.3.4 | Status of IPsec and On-Going | Work........................................................... 5-9 |\n| | 5.3.5 | Security Ramifications.............................................................................."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "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 Access Control?"}, {"role": "assistant", "content": "According to Guide to Integrating Forensic Techniques into Incident Response:\n\n| Publication Structure .............................................................................................\n| 1-2 |\n| | | 2-1 |\n| Establishing and Organizing a Forensics Capability.................................................. | Establishing and Organizing a Forensics Capability.................................................. | Establishing and Organizing a Forensics Capability.................................................. |\n| 2.1 | The Need for Forensics......................................................................................... | 2-1 |\n| 2.2 | Forensic Staffing ..................................................................................................."}], "metadata": {"source": "Guide to Integrating Forensic Techniques into Incident Response", "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 Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case:\n\nNetworking equipment - All coordination between workcell components occurs through the installed network equipment. If this equipment degrades or ceases to function, production goals will be impacted.\n| Reporting Method | Description | Frequency |\n|---------------------|------------------------------------------------------------------------------------------|--------------------------------------|\n| Risk Management log | A document to report the results of risk identification, analysis, and response planning | Yearly |\n| CSET Report | A document describing Risk assessment results | Yearly |\n| NamicSoft report | A document containing results of Nessus vulnerability scans. | Manual/Post vulnerability assessment |"}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "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 Access Control?"}, {"role": "assistant", "content": "According to Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products:\n\nain 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.\nHow an IoT product and its product components can be securely re-provisioned 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. Additional information customers can use to make informed purchasing decisions about the security of the IoT product (e.g., the duration and scope of product support via software upgrades and patches)."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report:\n\n| | Introduction: Workshop Objective, Participants, and Agenda.......................................1 |\n|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Workshop Session Highlights and Summaries................................................................5 |\n| HPC | Architecture and Security Posture ........................................................................5 |\n| | HPC Operator Security Experience...............................................................................6 |\n| | Risk Management Framework Development, Implementation, and Assessment.........7 |\n| 2.3.1."}], "metadata": {"source": "3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report", "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 Foundational Cybersecurity Activities for IoT Device Manufacturers support CMMC certification?"}, {"role": "assistant", "content": "According to Foundational Cybersecurity Activities for IoT Device Manufacturers:\n\nral 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. ## 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\nInternet of Things (IoT) devices often lack device cybersecurity capabilities their customersorganizations and individuals-can use to help mitigate their cybersecurity risks."}], "metadata": {"source": "Foundational Cybersecurity Activities for IoT Device Manufacturers", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines on Securing Public Web Servers:\n\nSecuring Web Content.....................................................................................................6-1 | |-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| | | 6.1 | Publishing Information on Public Web Sites | ............................................................6-1 | | | 6.2 | Observing Regulations about the Collection of Personal Information......................6-3 | | | | 6.3 | Mitigating Indirect Attacks on Content .....................................................................6-5 | | | | | 6.3.1 Phishing........................................................................................................6-5 | | | | | 6.3.2 Pharming | ......................................................................................................6-7 | | | 6.4 | Securing Active Content and Content Generation Technologies.............................6-8 | | | | | 6.4.1 Vulnerabilities with Client-Side Active Content Technologies | ....................6-10 | | | | 6.4.2 Vulnerabilities with Server-Side Content Generation Technologies...........6-12 | | | | | 6.4.3 Server-Side Content Generator Security Considerations...........................6-15 | | | | | 6.4.4 Location of Server-Side Content Generators | .............................................6-17 | | | | 6.4.5 Cross-Site Scripting Vulnerabilities | ............................................................6-17 | | | 6.5 | Checklist for Securing Web Content......................................................................6-18 | | | 7."}], "metadata": {"source": "Guidelines on Securing Public Web Servers", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Best Practices for Privileged User PIV Authentication:\n\nThis work resulted in the development of the CSIP [1]. A major gap identified by the CSIP is the delay in utilizing PIV credentials for logical access control and identity management on federal information systems, with an especially high priority for strengthening authentication for\n\nThe agency should compare the inventory to what is necessary to meet the organization's mission, and then remove all unnecessary privileged accounts, unnecessary permissions for privileged accounts, conflicting permissions for privileged accounts 11 , unnecessary user access to privileged accounts in accordance with the principle of least privilege and perform automated reviews of privileged user access. This should include, at a minimum, the following actions:\n\n1. Remove all privileged account access from users who no longer require access to perform their assigned duties (e.g., system, network, or database administration). 2. Remove or disable all privileged accounts, including default and built-in accounts, that are no longer required. 3. Remove excessive access to privileged accounts from privileged users in accordance with the principles of least privilege and separation of duties. Access should be evaluated in the context of enterprise risk, not just application risk. For example, granting a privileged user access to both portions of a sensitive personally identifiable information (PII) data set divided between two systems may create excessive risk to the organization. 4. Remove all unnecessary permissions from privileged accounts. This includes restricting which commands, functions, or other elements can be performed through privileged accounts. It may also include additional restrictions to more strongly limit the use of privileged accounts via remote access (in other words, allow certain actions to be performed only from dedicated, highly-secured endpoint devices). 5. Enforce a maximum single session length for use of each privileged account."}], "metadata": {"source": "Best Practices for Privileged User PIV Authentication", "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 Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies:\n\nvision, hearing, or speech. Immersive technologies pose great benefits for the nation and may be critical to several sectors in the future such as education, industrial maintenance, and entertainment.\nThat said, many aspects of the technology space and standards are nascent, hindering specific discussion of cybersecurity and privacy. Though there are questions that need consideration related to cybersecurity and privacy of immersive technologies, as noted in the Section 4, existing NIST risk management guidelines, tools, and resources can support risk-based and ethical decisionmaking in the development and use of immersive systems, products, and services. Thus, participants in immersive technology ecosystems (e.g., product manufacturers and providers, supporting service providers, institutional and individual users) can leverage the existing NIST cybersecurity and privacy portfolio, either directly or through tailoring and profiling. Through this mechanism, as NIST has done before, practical application of cybersecurity and privacy risk management can be supported in the near term with new projects and research directions potentially identified through continued community engagement."}], "metadata": {"source": "Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies", "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 Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping:\n\nKEY WORDS: authenticated encryption; authentication; block cipher; computer security; confidentiality; cryptography; encryption; information security; key wrapping; mode of operation."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\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\nThese guidelines do not give specific recommendations on steps that can be taken to make this determination. There are tools available (such as the Data Analytics Program [69]) that can provide information to system administrators that can be used to assess the impact of supporting or not supporting TLS versions prior to TLS 1.2. For example, DAP data on visitor OS and browser versions can help administrators determine what percentage of visitors to agency websites cannot negotiate recommended TLS versions by default."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice RA.L2-3.11.1 (NIST 3.11.1)?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 1 – General:\n\n3.11.1 Private Ephemeral Keys... 3.11.1 Private Ephemeral Keys\n\nPrivate ephemeral keys shall not be backed up or archived."}], "metadata": {"source": "Recommendation for Key Management_ Part 1 – General", "cmmc_level": "all", "nist_control": "3.11.1", "cmmc_practice_id": "RA.L2-3.11.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to 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 Personnel Security?"}, {"role": "assistant", "content": "According to Computer Security Division 2005 Annual Report:\n\nonal-level personnel. We also invite public and private organizations to submit their information security practices to be considered for inclusion on the list of practices maintained on the Web site.\nPolicies and procedures may be submitted to us in any area of information security, including accreditation, audit trails, authorization of processing, budget planning and justification, certification, contingency planning, data integrity, disaster planning, documentation, hardware and system maintenance, identification and authentication, incident handling and response, life cycle, network security, personnel security, physical and environmental protection, production"}], "metadata": {"source": "Computer Security Division 2005 Annual Report", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\n| | 5.3.3 | Distinguishing RSN and Pre-RSN WLANs.................................................5-11 | | |-----|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| | 5.4 | Authentication Phase.............................................................................................5-12 | Authentication Phase.............................................................................................5-12 | | | | 5.4.1 | The IEEE 802.1X Framework: Port-Based Access Control........................5-12 | | | | 5.4.2 | Authentication with the | PSK.......................................................................5-14 | | | 5.4.3 | AS to AP Connections................................................................................5-15 | | | | 5.4.4 | Pre-Authentication and PMKSA Caching | ...................................................5-17 | | 5.5 | Key Generation and Distribution ............................................................................5-18 | Key Generation and Distribution ............................................................................5-18 | | | | 5.5.1 | 4-Way Handshake......................................................................................5-18 | | | | 5.5.2 | Group Key Handshake | ...............................................................................5-19 | | | Protected Data Exchange......................................................................................5-20 | Protected Data Exchange......................................................................................5-20 | | | 5.7 | Connection Termination.........................................................................................5-21 | Connection Termination.........................................................................................5-21 | | | | Summary................................................................................................................5-21 | Summary................................................................................................................5-21 | | | 6."}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "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 BIOS Protection Guidelines:\n\n| 1."}], "metadata": {"source": "BIOS Protection Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Guide to General Server Security:\n\n3.2.2 Information Systems Security Program Managers... 3.2.2 Information Systems Security Program Managers\n\nThe Information Systems Security Program Managers (ISSPM) oversee the implementation of and compliance with the standards, rules, and regulations specified in the organization's security policy."}], "metadata": {"source": "Guide to General Server Security", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Verification and Test Methods for Access Control Policies_Models:\n\nn the policy, model, and safety requirements may each describe their own space of permission conditions, and may not be congruent in one space as the initial relation illustrated examples in Figure 7.\nThe safety and liveness check can assure only the logic integrity of some rules against some safety requirements. The complete satisfaction of a model to its policy requires repair of coverage and confinement faults if any violations are detected by additional Coverage and Confinement Check (CCC), the second line of defense against such semantic faults."}], "metadata": {"source": "Verification and Test Methods for Access Control Policies_Models", "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 Information Security Guide for Government Executives:\n\n| Information Security Program Elements | Information Security Program Elements | |-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Awareness and Training | The security awareness and training program is a critical component of the information security program."}], "metadata": {"source": "Information Security Guide for Government Executives", "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 Vetting the Security of Mobile Applications:\n\n| Functional Requirements | |----------------------------------------------------------------------| | Access to Platform Resources | | Anti-Exploitation Capabilities | | Cryptographic Key Functionality | | Cryptographic Operations | | Encryption of Sensitive Application Data | | Hyper Text Transfer Protocol Secure (HTTPS) | | Integrity for Installation and Update | | Network Communications | | Protection of Data in Transit | | Random Bit Generation | | Secure by Default Configuration | | Software Identification and Versions | | Specification of Management Functions | | Storage of Credentials | | Supported Configuration Mechanism | | Transport Layer Security Operations | | Use of Supported Services and Application Programming Interfaces | | Use of Third-Party Libraries | | User Consent for Transmission of Personally Identifiable Information | | X.509 Functionality | - Architecture, Design, and Threat Modeling Requirements - Data Storage and Privacy Requirements - Cryptography Requirements - Authentication and Session Management Requirements - Network Communication Requirements - Platform Integration Requirements - Code Quality and Build-Setting Requirements - Resilience Requirements | Criterion | Description | |------------------|-----------------------------------------------------------------------------------------------------------------------------| | Policies | The security, privacy and acceptable use policies; social media guidelines; and regulations applicable to the organization."}], "metadata": {"source": "Vetting the Security of Mobile Applications", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards:\n\n------|\n| Identify | ID. AM | Asset Management |\n| Identify | ID. BE | Business Environment |\n| Identify | ID.\nGV | Governance |\n| Identify | ID.RA | Risk Assessment |\n| Identify | ID.RM | Risk Management Strategy |\n| Identify | ID.SC | Supply Chain Risk Management |\n| Protect | PR.AC | Identity Management and Access Control |\n| Protect | PR.AT | Awareness and Training |\n| Protect | PR.DS | Data Security |\n| Protect | PR.IP | Information Protection and Procedures |\n| Protect | PR.MA | Maintenance |\n| Protect | PR.PT | Protective Technology |\n| Detect | DE.AE | Anomalies and Events |\n| Detect | DE.CM | Security Continuous Monitoring |\n| Detect | DE.DP | Detection Processes |\n| Respond | RS.RP | Response Planning |\n| Respond | RS.CO | Communications |\n| Respond | RS.AN | Analysis |\n| Respond | RS.MI | Mitigation |\n| Respond | RS.IM | Improvements |\n| Recover | RC.RP | Recovery Planning |\n| Recover | RC.IM | Improvements |\n| Recover | RC.CO | Communications |"}], "metadata": {"source": "Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards", "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 Computer Security Division 2014 Annual Report provide? (Part 5)"}, {"role": "assistant", "content": "| 11 | | CSD WORKIN NATIONAL AND INTERNATIONAL STANDARDS.................................................................................................12 | | | FEDERAL INFORMATION SECURITY MANAGEMENT ACT (FISMA) IMPLEMENTATION PROJECT...........................................16 | | | BIOMETRIC STANDARDS AND ASSOCIATED CONFORMITY ASSESSMENT TESTING TOOLS..................................................17 | | | FEDERAL CYBERSECURITY RESEARCH & DEVELOPMENT (R&D).............................................................................................19 | | | SECURITY ASPECTS OF ELECTRONIC VOTING...........................................................................................................................19 | | | HEALTH INFORMATION TECHNOLOGY SECURITY.....................................................................................................................20 | | | SUPPLY-CHAIN RISK MANAGEMENT (SCRM) FOR INFORMATION AND COMMUNICATIONS TECHNOLOGY (ICT)................21 | | | NATIONWIDE PUBLIC SAFETY BROADBAND NETWORK (NPSBN) CYBERSECURITY............................................................22 | | | SECURITY OF CYBER-PHYSICAL SYSTEMS (CPS) .....................................................................................................................23 | | | SMART GRID CYBERSECURITY...................................................................................................................................................24 | | | CYBERSECURITY AWARENESS, TRAINING, EDUCATION, AND OUTREACH............................................................................25 | | | National Initiative for Cybersecurity Education (NICE)............................................................................................................................25 Computer Security Resource Center (CSRC) | ..............................................................................................................................................26 | | Federal Computer Security Program Managers' Forum..........................................................................................................................."}], "metadata": {"source": "Computer Security Division 2014 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity:\n\nFor example, conformance testing captures the technical description of the requirements in a standard and measures whether an implementation (product, process or service) faithfully fulfills these requirements. Conformance testing alone does not completely ensure the interoperability or performance of conforming products, processes, or services. Therefore, interoperability and performance testing are also important aspects for procurements. Interoperability testing tests one implementation with another to establish that they can work together properly. Performance testing measures the performance characteristics of an implementation, such as its throughput 9 or response time, 10 under various conditions.\n\nIn some instances, testing and attestation of products, processes, and services against established cybersecurity standards may help provide a level of assurance that a product, process, or service's stated security claim is valid. An example is the USG requirement for using cloud products that meet Federal cloud security requirements. Commercial assessment organizations, which are accredited for assessing cloud security, determine if a cloud\n\nproduct conforms to the requirements. This can be more cost-effective for Federal agencies than developing inhouse USG testing expertise."}], "metadata": {"source": "Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity", "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 Computer Security Division 2012 Annual Report provide? (Part 3)"}, {"role": "assistant", "content": "|\n| Security Outreach and Integration Group................ | 5 |\n| Security Testing, Validation, and Measurement Group...\n| 6 |\n| The Computer Security Division Implements the Federal Information Security Management Act of 2002......................................................7 | |\n| CSD's Programs/Projects for FY2012..................8 | |\n| CSD Work in National and International Standards....."}], "metadata": {"source": "Computer Security Division 2012 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\nunities) can be listed in descending order of their enterprise benefit in a similar way. Prioritization and risk evaluation must also consider the positive risks that might evolve from an opportunity.\nRisk calculations are often based on analysis of both the cost of response and the benefit of proceeding. For example, while there have been many cybersecurity risks inherent to telework scenarios, organizations are increasingly realizing that a remote workforce brings positive benefits (e.g., reduced office space costs and utilities, reduced commuting time for employees, wider access to a skilled workforce). Understanding and calculating the various factors -such as through a strength, weakness, opportunity, and threat (SWOT) analysis -helps to prioritize all risks and evaluate available responses. Such an analysis must also keep in mind the consequences of failure to pursue an opportunity, even in light of certain negative risks. An organization that is considering creating a new product offering that works through a mobile device application must weigh the potential negative risks (e.g., intentional attacks by cyber criminals, software errors that might create customer support needs) against the positive risks (e.g., additional customer revenue and market share opportunities) made available through that offering. Basing risk considerations on benefits to and consequences on enterprise drivers supports mission-focused prioritization."}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report:\n\nIn the second presentation, Aron Warren from Sandia National Laboratories introduced the concept of a diskless HPC architecture. This innovative approach aims to minimize operational overhead while offering multiple advantages for enhancing security. By eliminating physical disks at most systems, it reduces the risk of data breaches or unauthorized access to sensitive information. Additionally, the diskless setup streamlines maintenance processes, reduces the attack surface, and enhances overall system resilience.\n\nIn summary, the panelists' recommendations emphasized the importance of comprehending the HPC operational environment. This includes documenting security and privacy requirements and keeping track of security and operational performance metrics, which will allow management to gain valuable insights into how well the HPC is performing in terms of both security and mission objectives. Furthermore, automation will help achieve consistent implementations for standardized and objective requirements. Tools like Gitlab and Ansible play a significant role in facilitating the maintenance and sharing of scripts that support the consistent implementation of security requirements unique to HPC environments.\n\n- Software-based encryption\n- Patching and software maintenance\n- Endpoint protection\n- Anti-virus software\n- Signature-based detection of malicious software"}], "metadata": {"source": "3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report", "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 Standard Security Label for GOSIP_ an Invitational Workshop:\n\n| 1. | INTRODUCTION | INTRODUCTION | INTRODUCTION | INTRODUCTION | INTRODUCTION | INTRODUCTION | 1 | INTRODUCTION | INTRODUCTION | INTRODUCTION | INTRODUCTION | INTRODUCTION |\n|------------------------------|-------------------------------|-------------------------------|-------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|----------------------------------|\n| 2. | REFERENCES | REFERENCES | REFERENCES | REFERENCES | REFERENCES | REFERENCES | 1 | REFERENCES | REFERENCES | REFERENCES | REFERENCES | REFERENCES |\n| 3. | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | 2 | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS | DEFINITIONS AND ABBREVIATIONS |\n| 4."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Approaches for Federal Agencies to Use the Cybersecurity Framework:\n\nSimilarly, the RMF also demonstrates this bilateral relationship. For example, every task within the Prepare step of the RMF aligns with the Cybersecurity Framework Core. Specifically, the P-2 Risk Management Strategy aligns with the Cybersecurity Framework Core [Identify Function at ID.RM; ID.SC]. Other RMF examples include: Task P-4, Organizationally-Tailored Control Baselines and Cybersecurity Framework Profiles, aligns with the Cybersecurity Framework Profile construct; and Task R-5, Authorization Reporting, and Task M-5, Security and Privacy Reporting, support OMB reporting and risk management requirements organizationwide by using the Cybersecurity Framework constructs of Functions, Categories, and Subcategories. 2\n\nBy aggregating cybersecurity findings, gaps, and vulnerabilities into a centralized record, agencies gain a combined view of cybersecurity risk and can make better informed risk decisions. Examples include determining how a system authorization decision might affect the agency as a whole, or how broader risk decisions might play out in a complex and connected infrastructure. An organization-wide record of risk enables consistent reporting. In some organizations, this centralized record is referred to as a 'risk register.' OMB Circular A-11 9 describes a risk register as 'a repository of risk information including the data understood about risks over time.' A-11 further explains, 'Typically, a risk register contains a description of the risk, the impact if the risk should occur, the probability of its occurrence, mitigation strategies, risk owners, and a ranking to identify higher priority risks' [15]. 10\n\nAgencies often track managed vulnerabilities, vulnerability mitigation plans, and accepted vulnerabilities on a system-by-system basis. This information is in the system Security Authorization Package, which includes the system security plan (SSP), the security assessment report (SAR), and the plan of action and milestones (POA&Ms). 11"}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile:\n\n| DATE | TYPE | CHANGE | PAGE | |------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| | 05-20-2019 | Editorial | Corrected contact information to indicate 'Applied Cybersecurity Division.' | i | | 05-20-2019 | Editorial | General formatting | All | | 05-20-2019 | Substantive | Changed '$1000' to 'Tens of thousands' in Table 7 | 14 | | 05-20-2019 | Substantive | Changed '$100,000' to 'Hundreds of thousands' in Table 7 | 14 | | 05-20-2019 | Substantive | Changed 'Minutes' to 'Hours' in Table 7 | 14 | | 05-20-2019 | Substantive | Deleted \"Military Contractors\" in Table 8 | 14 | | 05-20-2019 | Substantive | Deleted 'Address the security of protected information in its third-party relationships.' from ID.AM-5."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide for Conducting Risk Assessments:\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. A threat is any circumstance or event with the potential to adversely impact organizational operations and assets, individuals, other organizations, or the Nation through an information system via unauthorized access, destruction, disclosure, or modification of information, and/or denial of service. 22 Threat events are caused by threat sources. A threat source is characterized as: (i) the intent and method targeted at the exploitation of a vulnerability; or (ii) a situation and method that may accidentally exploit a vulnerability. In general, types of threat sources include: (i) hostile cyber or physical attacks; (ii) human errors of omission or commission; (iii) structural failures of organization-controlled resources (e.g., hardware, software, environmental controls); and (iv) natural and man-made disasters, accidents, and failures beyond the control of the organization. Various taxonomies of threat sources have been developed. 23 Some taxonomies of threat sources use the type of adverse impacts as an organizing principle."}], "metadata": {"source": "Guide for Conducting Risk Assessments", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0:\n\n3.4.3 | Threats TOE and Environment jointly address ... 3.4.3 as follows:\n\nTable 3. 3.4.3: Threats addressed jointly by the TOE and its environment\n\nTable 3."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Managing the Security of Information Exchanges:\n\nDespite the advantages, information exchange exposes the participating organizations to risk. If the information exchange is not properly planned and managed, a failure to protect the information from a loss of confidentiality, integrity, or availability could compromise the information and associated systems. Similarly, if one of the systems is compromised, the exchanged information could be compromised, or an interconnection used to exchange information could be leveraged as a conduit to compromise the other system and information. The risk is underscored because, in most cases, each participating organization has little or no control over the operation and management of the other\n\nThe less expensive alternative is to connect systems over a public network (e.g., the internet) using a VPN. A VPN is a network that enables two or more parties to communicate securely across a public network by creating a private connection, or 'tunnel,' between endpoints. Information transmitted via VPN over a public network can be intercepted by unauthorized parties. However, the use of authentication and encryption helps ensure the confidentiality and integrity of the information\n\n- Electronic/Digital File Transfers - Information can be exchanged via an electronic or digital file transfer, the transmission of a file (information) between two systems via a file transfer (communications) protocol. Organizations consider the risk associated with the use of different file transfer protocols; file transfer protocols include file transfer protocol secure (FTPS), Hypertext Transfer Protocol Secure (HTTPS), and Secure Copy Protocol (SCP). - Email - Organizations often share information via email as file attachments."}], "metadata": {"source": "Managing the Security of Information Exchanges", "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 Cryptographic Algorithms and Key Sizes for Personal Identity Verification:\n\n| Introduction...............................................................................................................................1 | Introduction...............................................................................................................................1 | Introduction...............................................................................................................................1 | Introduction...............................................................................................................................1 | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| | | Application of Cryptography in FIPS 201-3 ..................................................................................3 | Application of Cryptography in FIPS 201-3 ..................................................................................3 | | | | On-Card Cryptographic Requirements.........................................................................................5 | On-Card Cryptographic Requirements.........................................................................................5 | | | | 3.2.1."}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n........................................................ 1 | CHAPTERONE INTRODUCTION......................................................................................................\n1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ................................................................................................... | 1 |\n| 1.2 | TARGET AUDIENCE .................................................................................................................. | 2 |\n| 1.3 | ORGANIZATIONAL RESPONSIBILITIES ........................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to 2019 NIST_ITL Cybersecurity Program Annual Report:\n\nays. This project has resulted in\n\nThe Computer Forensics Tool Testing Program (CFTT) is a project of ITL's Software and Systems Division (SSD) and is supported by the Special Programs Office and DHS.\nIn FY 2019, several key advances were made to help address a critical need in the law enforcement community to ensure the reliability of computer forensic tools."}], "metadata": {"source": "2019 NIST_ITL Cybersecurity Program Annual Report", "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 Platform Firmware Resiliency Guidelines:\n\nPlatform and device manufacturers need to determine what level of event logging might be required for their systems, taking into account the intended users' environments for those systems. Events which are logged should be recorded in a manner which provides assurances of their integrity and allows for the secure recovery and transmission of logged events. Care must be taken to ensure event log access is controlled. Unauthorized personnel can use event log data analysis to broaden the attack surface."}], "metadata": {"source": "Platform Firmware Resiliency Guidelines", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective:\n\nmachine-readable vulnerability identification and metrics, platform and asset identification, actionable threat information and policy triggers for actions to respond to threats and policy violations.\nAutomated activities would include a Security Operation Center (SOC) to ensure autonomous and continuing monitoring and evolution of the security state of assets based upon prescribed events."}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Password-Based Key Derivation_ Part 1_ Storage Applications:\n\n| Approved | FIPS-approved and/or NIST-recommended. An algorithm or technique that is 1) specified in a FIPS or NIST Recommendation; or 2) adopted in a FIPS or NIST Recommendation; or 3) specified in a list of NIST-approved security functions. |\n|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Authenticated encryption | A function in which plaintext is encrypted into ciphertext, and a MACis generated on the plaintext or ciphertext and, optionally, on associated data that is not encrypted. |\n| Cryptographic algorithm | A well-defined computational procedure that takes variable inputs that may include a cryptographic key to provide confidentiality, data integrity, authentication and/or non-repudiation. |\n| Cryptographic key (key) | A binary string that is used as a parameter by a cryptographic algorithm. |\n| Data protection key | A key or a set of keys used to protect or recover data, verify the authenticity or integrity of the protected data or to protect the private key used to generate digital signatures. |\n| Decryption | The process of transforming ciphertext into plaintext using a cryptographic algorithm and key. |\n| Digest size | The output length of a hash function. |\n| Encryption | The process of transforming plaintext into ciphertext using a cryptographic algorithm and key. |\n| Entropy | A measure of the amount of uncertainty in an unknown value. |\n| Iteration count | The number of times that the pseudorandom function is called to generate a block of keying material . |\n| Key | See cryptographic key. |"}], "metadata": {"source": "Recommendation for Password-Based Key Derivation_ Part 1_ Storage Applications", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Stateful Hash-Based Signature Schemes:\n\nAn application that may fit this profile is the authentication of firmware updates for constrained devices. Some constrained devices that will be deployed in the near future will be in use for decades. These devices will need to have a secure mechanism for receiving firmware updates, and it may not be practical to change the code for verifying signatures on updates once the devices have been deployed. | [8] | McGrew D, Kampanakis P, Fluhrer S, Gazdag S, Butin D, Buchmann J (2016) State Management for Hash-Based Signatures. Cryptology ePrint Archive , Report 2016/357. https://eprint.iacr.org/2016/357.pdf |\n|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [9] | Genêt A, Kannwischer MJ, Pelletier H, McLauchlan A (2018) Practical Fault Injection Attacks on SPHINCS. Cryptology ePrint Archive , Report 2018/674. https://eprint.iacr.org/2018/674 |\n| [10] | Castelnovi L, Martinelli A, Prest T (2018) Grafting trees: A fault attack against the SPHINCS framework. Post-Quantum Cryptography - 9th International Conference (PQCrypto 2018) , Lecture Notes in Computer Science 10786, pp 165-184. https://doi.org/10.1007/978-3-319-79063-3_8 |\n| [11] | Fluhrer S (2017) Further Analysis of a Proposed Hash-Based Signature Standard . Cryptology ePrint Archive , Report 2017/553. https://eprint.iacr.org/2017/553.pdf |\n| [12] | Buchmann J, Dahmen E, Hulsing A (2011) XMSS - A Practical Forward Secure Signature Scheme based on Minimal Security Assumptions ."}], "metadata": {"source": "Recommendation for Stateful Hash-Based Signature Schemes", "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 Information Technology Security Services:\n\n3.4.2 Prepare and Review Systems Security Requirements\n\nThe Contractor shall prepare a list of system security requirements."}], "metadata": {"source": "Guide to Information Technology Security Services", "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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Foundations of a Security Policy for Use of the National Research and Educational Network:\n\nPolicy | 11 | | 2.5 | Projected View of the NREN | Projected View of the NREN | 11 | | | 2.5.1 | Long-Range View | 11 | | | 2.5.2 | Fundamental Characteristics | 12 | | | 2.5.3 | Constituency | 13 | | | 2.5.4 | Network Topology and Security Considerations | 14 | | | Conclusion | Conclusion | 15 | | 2.6 2.7 | References | References | 16 | | 3.1 | for a National Network Security Policy Introduction | for a National Network Security Policy Introduction | 18 | | 3.2 | Computer Information Security and Security Policies | Computer Information Security and Security Policies | 18 | | | 3.2.1 | Concept of Computer Information Security | 18 | | | 3.2.2 Specification of a Security Policy | 3.2.2 Specification of a Security Policy | 19 | | 3.3 | Ethical and Legal Considerations | Ethical and Legal Considerations | 19 | | 3.4 | Need for a National Network Security Policy | Need for a National Network Security Policy | 20 | | 3.5 | Examples of Existing Organizational Policies | Examples of Existing Organizational Policies | 22 |"}], "metadata": {"source": "Foundations of a Security Policy for Use of the National Research and Educational Network", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Privacy Protection in the United States_ A 1991 Survey of Laws and Regulations Affecting Privacy in the Public and Private Sector Including a List of :\n\n's records without the consent of the student (or the parent of a minor student) except for certain specified purposes, or pursuant to a court order or lawfully issued subpoena. 20 U.S.C. § 1232g. 22.\nSome States also have enacted statutes which place limitations on the ability of schools to disclose information from school records to third parties. See . e . q . Del. Code tit. 14, § 4111; Idaho Code § 9-203(6); Ky. Rev. Stat. § 421.216; Mich. Comp. Laws § 600.2165; N.C. Gen. Stat. § 8-53-4. 23. The NAIC Model Law (approved by the NAIC in December 1979 and enacted in 13 States since then) requires insurance companies and insurance agents to notify applicants about the collection and disclosure of personal data, and to specify when information is requested solely for marketing or research purposes. In addition, the Model Law restricts the use of \"pretext interviews\" (in which the identity or purpose of the interviewer is misrepresented) and requires specific consent forms to be used for the collection of information that requires authorization from an individual. A specific notice must also be given if information is collected via personal interviews with neighbors, acquaintances, or associates of an individual. See . e . q . Calif. Ins. Code § 791."}], "metadata": {"source": "Privacy Protection in the United States_ A 1991 Survey of Laws and Regulations Affecting Privacy in the Public and Private Sector Including a List of ", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs:\n\ntrustworthiness and guaranteed veracity of information. The possible values for this metric are: None (N), Partial (P), and Complete (C). Increased integrity impact increases the vulnerability score.\n| Metric | Evaluation | Score |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Access Vector Access Complexity Authentication Confidentiality Impact Integrity Impact Availability Impact --------------------------------------------------------------------------------------------------------------------- | [Local] [High] [None] [Complete] [Complete] [Complete] | --------------------------------------------------------------------------------------------------------------------- (0.395) (0.35) (0.704) (0.66) (0.66) (0.66) |"}], "metadata": {"source": "Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile:\n\n| Function Unique Identifier | Function | Category Unique Identifier | Category | |------------------------------|------------|------------------------------|-------------------------------------------------| | ID | Identify | ID.AM | Asset Management | | ID | Identify | ID.BE | Business Environment | | ID | Identify | ID.GV | Governance | | ID | Identify | ID.RA | Risk Assessment | | ID | Identify | ID.RM | Risk Management Strategy | | PR | Protect | PR.AC | Access Control | | PR | Protect | PR.AT | Awareness and Training | | PR | Protect | PR.DS | Data Security | | PR | Protect | PR.IP | Information Protection Processes and Procedures | | PR | Protect | PR.MA | Maintenance | | PR | Protect | PR.PT | Protective Technology | | DE | Detect | DE.AE | Anomalies and Events | | DE | Detect | DE.CM | Security Continuous Monitoring | | DE | Detect | DE.DP | Detection Processes | | RS | Respond | RS.RP | Response Planning | | RS | Respond | RS.CO | Communications | | RS | Respond | RS.AN | Analysis | | RS | Respond | RS.MI | Mitigation | | RS | Respond"}], "metadata": {"source": "Cybersecurity Framework Manufacturing 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 Level 3 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| ASSESSMENT PROCEDURES................................................................................................................\n| 3 |\n| 2.2 | ASSURANCE CASES.............................................................................................................................. | 4 |\n| CHAPTER THREE THE PROCEDURES............................................................................................... | CHAPTER THREE THE PROCEDURES............................................................................................... | 7 |\n| 3.1 | ACCESSCONTROL ............................................................................................................................... | 8 |\n| 3.2 | AWARENESSANDTRAINING............................................................................................................... | 9 |\n| 3.3 | AUDIT ANDACCOUNTABILITY........................................................................................................... | 10 |\n| 3.4 | CONFIGURATION MANAGEMENT....................................................................................................."}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\n| Attack Step Name | Attack Step Purpose (General) | Capability-Specific Examples |\n|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1) Gain Internal Entry | The attacker is outside the target boundaries and seeks entry. Examples include: spear phishing email sent; distributed denial of service (DDoS) attack against .gov initiated; unauthorized person attempts to gain physical access to restricted facility. | Block Local Access: Prevent or minimize compromised, vulnerable, or targeted software from entering or being stored on the network or devices in a way that would allow installation or execution. |\n| 3) Gain Foothold | The attacker has gained entry to the assessment object and achieves enough compromise to gain a foothold, but without persistence."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\ncredential; e-authentication; identity credential; issuance; personal identity verification (PIV); physical access control system (PACS); PIV authentication mechanisms; PIV cards; public key infrastructure (PKI); validation\n\nThis document is intended for government officials responsible for implementing Homeland Security Presidential Directive-12 (HSPD-12) compliant physical access control systems (PACS). Information in this document is also useful to government contractors and physical security vendors that provide HSPD-12 systems, products, and integration services. It is expected that readers have a general knowledge of PIV standards, including [FIPS 201-2], [SP800-73], and [SP800-78].\n\nMany changes in this document were made to align SP 800-116 with revision 2 of FIPS 201 (FIPS 201-2). For example, credential validation is now required (see Section 4.4). The CHUID authentication mechanism has been deprecated due to security concerns. For this reason, this publication marks the authentication mechanism as deprecated to signify that it is not a viable authentication mechanism to deploy for physical access control system (PACS). The CHUID data element on the PIV Card, however, remains a mandatory element as the BIO(-A) and SYMCAK authentication mechanisms use the data element as a source for the card's expiration date. It also provides unique identifiers for PACS ACLs. The previous version of this document also included the combined VIS + CHUID authentication mechanism as an option to transitioning from Unrestricted to Controlled areas. VIS + CHUID, however, is not included in this version of the document since it provides 'LITTLE or NO' confidence in the identity of the cardholder."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Guide to Information Technology Security Services:\n\n3.4.3 Perform Security Test and Evaluation 16 of System\n\nThe Contractor shall perform a security test and evaluation to demonstrate through appropriate verification techniques, verification procedures, and procedure refinements, that the management, operational, and technical security controls for the IT system are implemented correctly and are effective in their application."}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 additional guidance does Security Considerations for Remote Electronic UOCAVA Voting provide? (Part 5)"}, {"role": "assistant", "content": "|\n| 5 INTEGRITY................................................................................ 23 | 5 INTEGRITY................................................................................\n23 | 5 INTEGRITY................................................................................ 23 |\n| 5.1 | POTENTIAL BENEFITS | ....................................................................23 |\n| 5.2 | PROPERTIES ..............................................................................23 | |\n| 5.3 | THREATS TO INTEGRITY .................................................................27 | |\n| 5.4 | CURRENT AND EMERGING TECHNICAL APPROACHES.................................30 | |\n| 5.5 | OPEN I SSUES.............................................................................37 | |\n| 6 AVAILABILITY........................................................................... 38 | 6 AVAILABILITY..........................................................................."}], "metadata": {"source": "Security Considerations for Remote Electronic UOCAVA Voting", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Best Practices for Privileged User PIV Authentication:\n\nHomeland Security Presidential Directive 12 (HSPD-12) [4] mandated the development and use of a federal standard for identification and authentication of federal employees and contractors. HSPD-12's intent is to eliminate the 'wide variations in the quality and security of identification used to gain access.' The standard resulting from HSPD-12, Personal Identity Verification (PIV), is defined in Federal Information Processing Standards (FIPS) Publication 201 [5]. FIPS\n\nThis work resulted in the development of the CSIP [1]. A major gap identified by the CSIP is the delay in utilizing PIV credentials for logical access control and identity management on federal information systems, with an especially high priority for strengthening authentication for\n\nThe NIST Risk Management Framework (RMF) [12] specifies the security risk management activities that an agency should perform throughout the system development lifecycle. The RMF references the associated standards and guidelines necessary to categorize system risk, select and implement security controls, and assess, monitor, and enhance their efficacy over time."}], "metadata": {"source": "Best Practices for Privileged User PIV Authentication", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3:\n\nInventory scanning can also be applied to collect information on the presence of software artifacts on systems, such as malware or characteristics of malware that indicate its presence. SCAP content authored for this purpose can be used to detect classes or categories of malware based on system state that may be common across multiple malware instances. For example, it is a common practice to reuse malware code, making modifications to address available detection methods, change propagation characteristics, etc. It is also possible to author content that detects a specific instantiation of malware. For example, hashing of files can be used to identify a malicious executable or library.\n\n- An OVAL inventory definition. This definition SHALL be contained in an OVAL component, which holds definitions of technical procedures for determining whether or not a specific target asset has software (product, platform, malware, etc.) of interest. An XCCDF benchmark's rules MAY reference one or more OVAL inventory class definitions in an OVAL component.\n- An OCIL questionnaire. This questionnaire SHALL be contained in an OCIL component, which holds questionnaires that collect information that OVAL is not being used to collect, such as posing questions to users or harvesting inventory information from an existing database. An XCCDF benchmark's rules MAY reference one or more OCIL questionnaires in an OCIL component.\n\n- o Revised legacy support requirements for SCAP content and OVAL definition documents.\n- o Added an SCAP result data stream subsection. Added source and result data stream requirements throughout the section. Also added a subsection on digitally signing result data stream content.\n- o Added a declaration of the FDCC Reporting Format.\n- In Section 5, added malware detection material to the Inventory Scanning use case.\n- Updated the normative references.\n- Added Appendix C (change log)."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3", "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 CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.4.4. 3.4.4). 3.4.4)\nwith a defined and implementable set of assurance levels and a final set of\ncontrols for the online service."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.4.4", "cmmc_practice_id": "CM.L2-3.4.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | |---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | | Introduction | ......................................................................................................................1-1 | | | | 1.1 | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope | | | | 1.3 | .................................................................................................1-1 Audience..................................................................................................................1-1 | | | | 1.4 | Document Structure.................................................................................................1-1 | | | | 1.5 | How to Navigate This Document .............................................................................1-2 | | | | Overview of Wireless Networking | ..................................................................................2-1 | | | | 2.1 | History of Wireless Networking Standards...............................................................2-1 | | | | | 2.1.1 IEEE 802.11 Standards................................................................................2-1 | | | | | 2.1.2 Wi-Fi Alliance Certification............................................................................2-2 | | | | | 2.1.3 Other Wireless Standards | ............................................................................2-3 | | | 2.2 | IEEE 802.11 Network Components and Architectural Models.................................2-4 | | | | | 2.2.1 Ad Hoc Mode................................................................................................2-4 | | | | | 2.2.2 Infrastructure Mode ......................................................................................2-6 | | | | 2.3 | Summary..................................................................................................................2-6 | | | | Overview | of IEEE 802.11 Security ..................................................................................3-1 | | | | 3.1 | WLAN Security Concerns ........................................................................................3-1 | | | | 3.2 | History of Pre-RSN IEEE 802.11 Security ...............................................................3-2 | | | | | 3.2.1 Access Control and Authentication...............................................................3-2 | | | | | 3.2.2"}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.2.4, 3. 3.2.4, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2:\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."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.4.2. 3.4.2."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to 2016 NIST_ITL Cybersecurity Program Annual Report:\n\nThe CSRC website is a vast repository of valuable information relating to cybersecurity research by NIST personnel in ITL and is one of the busiest and most expansive websites at NIST. CSRC encourages the broad sharing of information security tools and practices, provides a resource for information security standards and guidelines, and identifies and links key security web resources to support industry and government users. Several divisions within ITL rely on the CSRC website to post program/project\n\nTo help address information security risks, these businesses require assistance with the identification of security mechanisms and with practical, cost-effective training. Training helps SMB's use their limited resources most effectively to address relevant and serious threats. In response to this need, NIST, the SBA, and the FBI InfraGard program co-sponsor a series of cybersecurity training workshops for small businesses. These workshops provide an overview of cybersecurity threats, vulnerabilities, and corresponding protective tools and techniques, with a special emphasis on information that small business personnel can apply directly. The CMVP strengthened its relationship with the CMUF by supporting the monthly CMUF general membership meetings and five CMUF working groups. The working groups are chaired by a member of industry and/or by laboratory personnel. Each working group includes a representative from the CMVP. The current working group topics include the Security Policy Template; Testing Equivalency; Revalidation in Response to Common Vulnerabilities and Exposures (CVEs); Proposed IG Integrity Testing using Random Sampling and IG Updates (IG 3.5 Documentation Requirements for Cryptographic Module Services, IG 1.20 Sub-Chip Cryptographic Subsystems, and 7.7 Key Establishment and Key Entry and Output)."}], "metadata": {"source": "2016 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series:\n\nthe block cipher using the given key. Rogaway [74] is correct to point out that the uniqueness of FIPS 81. Lipmaa et al. [51] argued for the inclusion of the CTR mode in NIST SP 800-38A and stated that 'a well-designed standard for the CTR mode should not be overly prescriptive about how [the counter blocks are] formed.' However, Rogaway does point out in Section 5.6.6 of [74] that the CTR specification may be too open-ended, which makes it more likely that an implementation of the CTR mode may be provided with a non-unique sequence of counter blocks. Rogaway then points out that compliance testing may suffer as well. Indeed, NIST's Advanced Encryption Standard Algorithm Validation Suite (AESAVS) document [12] states that 'it is not possible to implement an automated test for [the CTR] mode' and requires a manual review of the design and implementation of the CTR mode in addition to performing the automated tests for the ECB mode. one-time pad (OTP). An adversary who knows certain plaintext blocks can use the ciphertext to derive all other plaintext blocks at locations where the counter blocks are reused by means of a\n\nIwata et al. [43] showed that the original proof of security for GCM was flawed as well as how variable-length nonces. Consequently, some protocols such as TLS 1.3 only allow GCM with a to 'repair' it. They also showed that GCM has better security bounds for 96-bit nonces than for 96-bit nonce. Another shortcoming of GCM is that the maximum plaintext length is 2 39 -256 bits, which is about 64 GiB (gibibytes). As with CCM, the limitation is due to the underlying CTR mode: going beyond the limit leads to a complete breakdown in security, which is similar to the reuse of a one-time pad. Files of more than 64 GiB are not unusual in video editing and genomics research, but they cannot be encrypted using the GCM mode."}], "metadata": {"source": "Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Labels for Open Systems_ an Invitational Workshop:\n\nThe Basic Security Option is required on each datagram, and if the data being transmitted falls within any of the DOE defined Categories or Handling Instructions, then an Extended Security Option is required as well. These Security Options contain orthogonal components of the security label . The Basic Security Option contains the security level and the Extended Security Option contains the security categories and handling instructions, which are collocated so that they can be treated as a single bit mask, if so desired. (In fact, a number of B1 systems currently available or under development represent security categories and compartments internally as a bit mask of 32, 64, or 128 bits. This would map well into the DOE label format and would permit a simple, efficient implementation of network security labeling.)\n\n2 = FOUO or Sensetive but Unclassified. This leaves room on either side of this level to introduce a new hierarchical level. Since there have been several recent developments in the \"sensitive but unclassified\" arena, additional levels in this region are more likely than for other levels.\n\nJohn Linn Secure Systems Development Digital Equipment Corporation Boxborough, MA 30 May 1990"}], "metadata": {"source": "Security Labels for Open Systems_ an Invitational Workshop", "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 Information Security Handbook_ A Guide for Managers:\n\n| 9.6 | Step 6: Plan Testing, Training, and Exercises ..........................................................82 | Step 6: Plan Testing, Training, and Exercises ..........................................................82 | | |------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------| | 9.7 | Step 7: Plan Maintenance .........................................................................................82 | Step 7: Plan Maintenance .........................................................................................82 | | | 10."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Representation of PIV Chain-of-Trust for Import and Export:\n\niction> \n\n## NIST Special Publication 800-140E\n\n## CMVP Approved Authentication Mechanisms:\n\nCMVP Validation Authority Requirements for ISO/IEC 19790 Annex E and ISO/IEC 24579 Section 6.17\n\nKim Schaffer Computer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-140E\n\nMarch 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 for Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official."}], "metadata": {"source": "CMVP Approved Authentication Mechanisms_ CMVP Validation Authority Requirements for ISO_IEC 19790 Annex E and ISO_IEC 24579 Section 6.17", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to Intrusion Detection and Prevention Systems (IDPS) provide?"}, {"role": "assistant", "content": "\n\n## Guide to Intrusion Detection and Prevention Systems (IDPS)\n\n## Recommendations of the National Institute of Standards and Technology\n\nKaren Scarfone Peter Mell\n\nNIST Special Publication 800-94\n\nGuide to Intrusion Detection and Prevention Systems (IDPS)\n\nRecommendations of the National Institute of Standards and Technology\n\nKaren Scarfone Peter Mell\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nFebruary 2007\n\n\n\n## U.S. Department of Commerce\n\nCarlos M. Gutierrez, Secretary\n\n## Technology Administration\n\nRobert C. Cresanti, Under Secretary of Commerce for Technology\n\nNational Institute of Standards and Technology\n\nWilliam Jeffrey, Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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. National Institute of Standards and Technology Special Publication 800-94 Natl. Inst. Stand. Technol. Spec. Publ."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 An Introduction to Privacy Engineering and Risk Management in Federal Systems provide? (Part 3)"}, {"role": "assistant", "content": "oncepts establish the basis for a common vocabulary to facilitate better understanding and communication of privacy risk within federal systems, and the effective implementation of privacy principles.\nThis publication introduces two key components to support the application of privacy engineering and risk management: privacy engineering objectives and a privacy risk model. ## Keywords\n\nComputer security; cybersecurity; information security; privacy; risk management; systems engineering\n\n## Acknowledgements\n\nThe authors wish to thank the following individuals for participating in the preparation of this document: Jeremy Berkowitz, James Dever, Simson Garfinkel, Meredith Jankowski, and Colin Soutar. They'd also like to recognize Kelley Dempsey, Marc Groman, Mat Heyman, Kat Megas, Rebecca Richards, and Ron Ross for their role in the review process. The authors are particularly grateful to Simson Garfinkel, who was so generous with his time and thoughtful feedback. A special note of thanks goes to Kaitlin Boeckl, who developed the graphics found herein. And finally, in developing the privacy risk model, the authors greatly appreciate the insights from the pilot programs funded by NIST pursuant to the National Strategy for Trusted Identities in Cyberspace (NSTIC). ## Executive Summary\n\nNIST research in information technology-including cybersecurity, cloud computing, big data, and the Smart Grid and other cyber-physical systems-aims to improve the innovation and competitiveness that bring great advancements to U.S. national and economic security and quality of life. Much of this research pertains to the trustworthiness of these information technologies and the systems in which they are incorporated."}], "metadata": {"source": "An Introduction to Privacy Engineering and Risk Management in Federal Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Automation Support for Security Control Assessments_ Software Vulnerability Management:\n\n3.4.3 | 3. 3.4.3 Control Item SA-11(d): DEVELOPER SECURITY TESTING AND EVALUATION\n\n## Control Item Text\n\nControl: The organization requires the developer of the information system, system component, or information system service to:\n\n- d. 3.4.3 High Baseline Control Allocation Table\n\nTable 10: High Baseline Control (Item) Allocation Table\n\n| Determination Statement ID | Implemented By | Assessment Boundary | Assessment Responsibility | Assessment Methods | Selected | Rationale for Risk Acceptance | Frequency of Assessment | Impact of Not Implementing |\n|------------------------------|------------------|-----------------------|-----------------------------|----------------------|------------|---------------------------------|---------------------------|------------------------------|\n| SI-2(1){1} | SWFM | ISCM-TN | ISCM-Sys | Test | | | | |\n\n| References | |\n|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [CNA] | The MITRE Corporation (2019) CVE Numbering Authorities."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Vulnerability Management", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Security Labels for Open Systems_ an Invitational Workshop:\n\nSecure Systems Strategy & Planning IBM Corporation uunet!pyrdc!ibmsid!vasu (301) 240-3716"}], "metadata": {"source": "Security Labels for Open Systems_ an Invitational Workshop", "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 Trustworthy Email:\n\n�e certificate given above is an example of an end certificate . Although it claims to be signed by a wellkn own CA, anyone receiving this certificate in communication has the problem of authenticating that signature. For this, full PKIX authentication back to the root certificate is required. �e CA issues a wellknown selfsigned certificate containing its public key . �is is the root certificate . A set of current root certificates, often numbering in the hundreds of certificates , are held by individual browser developers and operating system suppliers as their set of trusted root certificates . �e process of authentication is the process of tracing the end certificate back to a root certificate, through a chain of zero or more intermediate certificates. For years, TLS has solved the problem of distributing public keys by using a certificate, signed by some wellknown Certification Authority (CA). Every browser developer and operating system supplier maintain a list of CA root certificates as trust -anchors. �ese are called the software's root certificates and are stored in the root certificate store . �e PKIX procedure allows the certificate recipient to trace a certificate back to the root . So long as the root certificate remains trustworthy, and the authentication concludes successfully, the client can proceed with the connection."}], "metadata": {"source": "Trustworthy Email", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security Analysis of First Responder Mobile and Wearable Devices:\n\nSource: NPSTC #2.7, SAFECOM 3.3.1, FirstNet 4.8.4\n\nThe officer may have unauthorized access to sensitive information that was authorized for a previous user. Additionally, accidentally collected Personally Identifiable Information (PII) may be exposed, and QPP values may be incorrectly assigned (e.g., higher priority incorrectly assigned to a lower priority user). Location data and health information may also be incorrectly associated with the previous user. The audit logs for the device or applications may be inaccurate. Availability concerns exist if the single sign-on (SSO) service goes down and the device needs to quickly be used for an emergency.\n\noperational state. To continue their duties, the firefighter uses their personal mobile device to conduct needed tasks, including downloading and logging into public safety applications."}], "metadata": {"source": "Security Analysis of First Responder Mobile and Wearable 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 Awareness and Training?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Science Challenges:\n\n| EXECUTIVE SUMMARY.................................................................................................................................... VIII | EXECUTIVE SUMMARY.................................................................................................................................... VIII | EXECUTIVE SUMMARY.................................................................................................................................... VIII |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| INTRODUCTION......................................................................................................................................... 2 | INTRODUCTION......................................................................................................................................... 2 | INTRODUCTION........................................................................................................................................."}], "metadata": {"source": "NIST Cloud Computing Forensic Science Challenges", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3:\n\n3.2.1 | General... 3.2.1 General\n\nThe @xml:base attribute SHALL NOT be allowed in XCCDF content."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\n| 1.1 Scope................................................................................................................\n| 1 |\n| | 1.2 Related DevSecOps Initiatives.......................................................................... | 3 |\n| | 1.3 Target Audience................................................................................................ | 4 |\n| | 1.4 Relationship to Other NIST Guidance Documents............................................ | 4 |\n| | 1.5 Organization of This Document........................................................................."}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "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 Personnel Security?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\n| ID.AM-1: Physical devices and systems within the organization are inventoried ISO/IEC 27001:2013 A.8.1.1, A.8.1.2 NIST SP 800-53 Rev. 5 CM-8, PM- 5 | An inventory of physical devices should be undertaken, reviewed, and maintained to ensure these devices are not vulnerable to ransomware. It is also beneficial to have a hardware inventory during the recovery phases after a ransomware attack, should a re- installation of applications be necessary. |\n| Asset Management (ID.AM): The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to organizational objectives and the organization's risk strategy. | ID.AM-2: Software platforms and applications within the organization are inventoried ISO/IEC 27001:2013 A.8.1.1, A.8.1.2 NIST SP 800-53 Rev. 5 CM-8, PM- 5 | Software inventories may track information such as software name and version, devices where it is currently installed, last patch date, and current known vulnerabilities. This information supports the remediation of vulnerabilities that could be exploited in ransomware attacks. |\n| Asset Management (ID.AM): The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to organizational objectives and the organization's risk strategy. | ID.AM-3: Organizational communication and data flows are mapped ISO/IEC 27001:2013 A.13.2.1, A.13.2.2 NIST SP 800-53 Rev. 5 AC-4, CA- 3, CA-9, PL-8 | This helps to enumerate what information or processes are at risk, should the attackers move laterally within an environment."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop:\n\nusage) to home IoT devices may result in increased costs, design changes, or have an impact on functionality. Mark Haney gave an example of having to charge a smart watch battery daily versus weekly.\nPanelist Andrew Tierney gave another example using multi-factor authentication (MFA): 'MFA represents a massive security improvement and stops password phishing. However, because consumers don't want barriers, some companies are hurt by deploying MFA. Consumers will go elsewhere.' These examples illustrate what can occur when"}], "metadata": {"source": "Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop", "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 Access Control?"}, {"role": "assistant", "content": "According to Program Review for Information Security Management Assistance (PRISMA):\n\nIntroduction .........................................................................................................................1 | |----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Purpose.......................................................................................................................1 | | | | 1.2 | Legislative Background...............................................................................................2 | | | | 1.3 | PRISMA......................................................................................................................2 | | | | 1.4 | PRISMA Assumptions and Constraints ......................................................................3 | | | | 1.5 | Audience.....................................................................................................................4 | | | | 1.6 | Document Organization | ..............................................................................................4 | | 2."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "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 A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\n| | 6.7.2 Restricting Cryptographic Module Entry and Output of Plaintext | Keys............................................................................................65 |\n|---------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|\n| | 6.7.3 Controlling Human Input.....................................................................65 | |\n| | 6.7.4 Multiparty Control | ...............................................................................66 |\n| | 6.7.5 Key Splitting | .......................................................................................66 |\n| 6.8 | Compromise Recovery ................................................................................."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements:\n\n3.3.1 SCAP Validation Tool' to '3. 3.3.1 SCAP Validation Tool' with '3. 3.3.1 SCAP Validation | Tool..."}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2:\n\n| Executive Summary................................................................................................................... 1 | Executive Summary................................................................................................................... 1 | Executive Summary................................................................................................................... 1 | Executive Summary................................................................................................................... 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ........................................................................................................................ | 1. Introduction ........................................................................................................................ | 1. Introduction ........................................................................................................................"}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2", "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 System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for Evaluating Differential Privacy Guarantees:\n\nng on its own, but as features accumulate they inevitably become uniquely identifying in combination. As a result, de-identified data nearly always contains some information that could be identifying.\nFor decades, it was considered prohibitively challenging to recover enough information from properly de-identified data to seriously compromise an individual's privacy [4]. However, the increasing availability of large amounts of data has led to the development of more powerful privacy attacks that disprove this assumption."}], "metadata": {"source": "Guidelines for Evaluating Differential Privacy Guarantees", "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 Key Performance Indicators for Process Control System Cybersecurity Performance Analysis provide?"}, {"role": "assistant", "content": "## NISTIR 8188\n\n## Key Performance Indicators for Process Control System Cybersecurity Performance Analysis\n\nCheeYee Tang\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8188\n\n\n\n## NISTIR 8188\n\n## Key Performance Indicators for Process Control System Cybersecurity Performance Analysis\n\nCheeYee Tang Intelligent Systems Division Engineering Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8188\n\nAugust 2017\n\n\n\nU.S. Department of Commerce Wilbur L."}], "metadata": {"source": "Key Performance Indicators for Process Control System Cybersecurity Performance Analysis", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Security baselines are groups of settings used to configure a system to meet a target level or set of requirements or to verify that a system complies with requirements. The mSCP seeks to simplify the macOS security development cycle by reducing the amount of effort required to implement security baselines. This collaboration between federal agencies minimizes duplicate effort that would otherwise be needed for these agencies to administer individual security baselines."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators:\n\nthe DRBG mechanism. The randomness source can be an entropy source or an RBG. |\n| Reseed | To acquire additional bits that will affect the internal state of the DRBG mechanism.\n|\n| Secure Channel | A path for transferring data between two entities or components that ensures confidentiality, integrity and replay protection, as well as mutual authentication between the entities or components. The secure channel may be provided using approved cryptographic, physical or procedural methods, or a combination thereof. Sometimes called a trusted channel. |\n| Security Strength | A number associated with the amount of work (that is, the number of operations of some sort) that is required to break a cryptographic algorithm or system in some way. In this Recommendation, the security strength is specified in bits and is a specific value from the set {112, 128, 192, 256}. If the security strength associated with an algorithm or system is S bits, then it is expected that (roughly) 2 S basic operations are required to break it. |\n| Seed | Noun : A string of bits that is used as input to a DRBG mechanism. The seed will determine a portion of the internal state of the DRBG, and its entropy must be sufficient to support the security strength of the DRBG. Verb : To acquire bits with sufficient entropy for the desired security strength. These bits will be used as input to a DRBG mechanism to determine a portion of the initial internal state. |"}], "metadata": {"source": "Recommendation for Random Number Generation Using Deterministic Random Bit Generators", "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 Building Secure Microservices-based Applications Using Service-Mesh Architecture provide? (Part 4)"}, {"role": "assistant", "content": "The distributed cross-domain nature of microservices needs secure token service (STS), key management and encryption services for authentication and authorization, and secure communication protocols.\nThe ephemeral nature of clustered containers (by which microservices are implemented) calls for secure service discovery. The availability requirement calls for: (a) resiliency techniques, such as load balancing, circuit breaking, and throttling, and (b) continuous monitoring (for the health of the service). The service mesh is the best-known approach that can facilitate specification of these requirements at a level of abstraction such that it can be uniformly and consistently defined while also being effectively implemented without making changes to individual microservice code. The purpose of this document is to provide deployment guidance for proxy-based Service Mesh components that collectively form a robust security infrastructure for supporting microservices-based applications. ## Keywords\n\nAPI gateway; Application Programming Interface (API); circuit breaker; load balancing; microservices; Service Mesh; service proxy. ## Acknowledgements\n\nThe authors like to express their sincere thanks to Brandon Lum, Senior Software Engineer at IBM Thomas J. Watson Research Center for his extensive, insightful feedback. They also express thanks to Isabel Van Wyk of G2-Inc and Tia Lo u den of Tetrate Inc. for their detailed editorial review. ## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Building Secure Microservices-based Applications Using Service-Mesh Architecture", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Computer Security Log Management provide? (Part 3)"}, {"role": "assistant", "content": "stitutes of Health, and the Social Security Administration, for their valuable comments and suggestions. ## Trademarks\n\nAll names are registered trademarks or trademarks of their respective companies.\n## Table of Contents\n\n| Executive Summary............................................................................................................ES-1 | Executive Summary............................................................................................................ES-1 | Executive Summary............................................................................................................ES-1 | |\n|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|\n| 1. | Introduction | ................................................................................................................... | 1-1 |\n| | 1.1 | Authority................................................................................................................"}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems:\n\nAs an emerging field, weaknesses may become evident that negate otherwise apparent advantages, or other data models may emerge with even greater benefit. Blockchain infrastructures, identity management platforms, and related user tools are still maturing, with efforts being developed to improve scalability and reliability. While the time for most readers to deploy these capabilities lies somewhere in the future, the capabilities and architecture designs discussed in this paper represent a potential new paradigm for digital identity, which could remodel or even replace traditional and federated identity management systems. Therefore, this field deserves careful consideration and scrutiny today, and this paper is intended to provide the foundational tools to enable such an ongoing evaluation.\n\n- Banking: account opening, fraud prevention, compliance with anti-money laundering (AML) and KYC laws, proof of funds, credit risk evaluation, as well as ownership, exchange, and trading of financial assets\n- Data brokerage: exchanges of datasets\n- Supply chain management: asset traceability and lifecycle, networks of sensors, and the Internet of Things\n- Education: issuance of transcripts, diplomas, and certifications that can then serve as verifiable credentials in job applications\n- Healthcare: issuance of prescriptions, submission of claims to health insurance, and sharing of health records\n- Government services: issuance of driver's licenses and birth certificates, maintenance of public registries of voters\n- Public safety: management of sets of equipment and reliable communication permissions\n- Manufacturing: representation of ownership of 3D models\n- Transportation: identification of autonomous vehicles"}], "metadata": {"source": "A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guidelines on Mobile Device Forensics provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-101 Revision 1\n\n## Guidelines on Mobile Device Forensics\n\nRick Ayers Sam Brothers Wayne Jansen http://dx.doi.org/10.6028/NIST.SP.800-101r1\n\n\n\n## NIST Special Publication 800-101 Revision 1\n\n## Guidelines on Mobile Device Forensics\n\nRick Ayers Software and Systems Division Information Technology Laboratory\n\nSam Brothers U.S. Customs and Border Protection Department of Homeland Security Springfield, VA\n\nWayne Jansen Booz Allen Hamilton McLean, VA\n\nhttp://dx.doi.org/10.6028/NIST.SP. 800-101r1\n\nMay 2014\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Management Act of 2002 (FISMA), 44 U.S.C. § 3541 et seq., Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment:\n\n3.1.1 ISCM Program Assessment Plan... 3.1.1 ISCM Program Assessment Plan... 3.1.1 ISCM Program Assessment Plan\n\nThe ISCM Program Assessment Plan guides the execution of the ISCM program assessment."}], "metadata": {"source": "Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Trustworthy Email provide? (Part 5)"}, {"role": "assistant", "content": "anization. For most of this document, it will be assumed that the organization has some or all responsibility for email and can configure or manage its own email and Domain Name System (DNS) systems .\nEven if this is not the case, the guidelines and recommendations in this document may help in education about email security and can be used to produce a set of requirements for a contracted service. ## Trademark Information\n\nAll registered trademarks belong to their respective organizations. ## Executive Summary\n\n�is document gives recommendations and guidelines for enhancing trust in email . �e primary audience includes enterprise email administrators, information security specialists and network managers. �is guideline applies to federal IT systems and will also be useful for small or medium sized organizations. Email is a core application of computer networking and has been such since the early days of Internet development. In those early days, networking was a collegial, research -oriented enterprise. Security was not a consideration. �e past forty years have seen diversity in applications deployed on the Internet, and worldwide adoption of email by research organizations, governments, militaries, businesses and individuals. At the same time there has been an associated increase in (Internet-based) criminal and nuisance threats. �e Internet's underlying core email protocol, Simple Mail Transport Protocol (SMTP), was first adopted in 1982 and is still deployed and operated today. However, this protocol is susceptible to a wide range of attacks including man -in-themiddle content modification and content surveillance. �e basic standards have been modified and augmented over the years with adaptations that mitigate some of these threats. With spoofing protection, integrity protection, encryption and authentication, properly implemented email systems can be regarded as sufficiently secure for governme nt, financial and medical communications."}], "metadata": {"source": "Trustworthy Email", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT):\n\n| Objects | Information Resources | Information Resources | Systems | Intelligent Computing Services | |---------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | • Home telehealth • Medical devices • Health and wellness products | • HL7 Fast Healthcare Interoperability Resource (FHIR) • Structural and semantic standards (vocabularies, code and value sets) • Actuators that receive commands • Personally worn physiological sensors | • HL7 Fast Healthcare Interoperability Resource (FHIR) • Structural and semantic standards (vocabularies, code and value sets) • Actuators that receive commands • Personally worn physiological sensors | • Payment • Research (system of systems) • Personal health records • Treatment o Electronic health records o Monitoring | • Learning Health System o Big data o High performance computing o Knowledge access o Natural language processing o Transformation o Longitudinal monitoring of patient progress o Adverse event monitoring o Translation | | People | People | People | People | People | | • Patients o Patient representatives o Health conscious individuals | • Patients o Patient representatives o Health conscious individuals | • Licensed Healthcare Providers: o Audiologists, o Dentists o Dietitians o Optometrists o Physicians o Nurses o Technicians/ Technologists | Therapists |  Non-Licensed Healthcare Providers: o Administrative personnel o"}], "metadata": {"source": "Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cloud Computing Synopsis and Recommendations:\n\nThere have been several well-publicized regional Internet outages that have been the result of denial of service attacks, viruses infiltrating web servers, worms taking down DNS servers, failures in undersea cables, and fiber optic cables being damaged during earthquakes and subsequent mudslides. Although these outages are relatively infrequent, they can have an impact on network connectivity for hours. Contingency planning for these rare but often serious outages should be addressed as part of any organization's tactical IT plans. Most substantial applications are using the Internet today regardless of whether cloud computing is employed; therefore the reader should not assume that by avoiding a cloud a user automatically avoids risks associated with Internet outages. Thus clarity as to how to divide the roles and responsibilities of implementing security controls is important to help organizations: (1) define detailed security plans to address cloud security requirements, (2) develop or procure appropriate security measures during development, (3) objectively compare and evaluate providers, and (4) execute security protocols during the deployment and throughout operation. In addition, collaboration between providers and consumers can help ensure that clouds meet specific security conformance and regulatory requirements, especially for those supporting government agency operations."}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "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 System and Network Security Acronyms and Abbreviations provide? (Part 5)"}, {"role": "assistant", "content": "ally found in an appendix) for definitions applicable to that particular document. The following conventions have been used in the preparation of the list of acronyms and abbreviations in this report.\n-  Abbreviations and acronyms generally appear in all capital letters, although there are occasional exceptions-for example, meter (m) and decibels referenced to one milliwatt (dBm). -  Technical terms are not capitalized unless they are proper nouns. Names of people, places, and groups, and the titles of protocols, standards, and algorithms are considered proper nouns. For example, certification and accreditation (C&A) is not capitalized, but Advanced Encryption Standard (AES) is capitalized. -  Collective nouns are not capitalized (e.g., wide area network [WAN]). -  When two or more definitions of the same acronym or abbreviation are given, the acronym or abbreviation is italicized and repeated for each definition. Definitions are listed alphabetically. ## 2. Acronym and Abbreviation List\n\nThis section consists of a list of selected system and network security acronyms and abbreviations, along with their generally accepted definitions. When there are multiple definitions for a single term, the acronym or abbreviation is italicized and each definition is listed separately."}], "metadata": {"source": "System and Network Security Acronyms and Abbreviations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions:\n\n| Specification of χ ................................................................................................................15 | | | | 3.2.5 | Specification of ι.................................................................................................................15 | | | | 3.3 KECCAK- p [ b , n r ] ..............................................................................................................................16 | 3.3 KECCAK- p [ b , n r ] ..............................................................................................................................16 | | | | 3.4 COMPARISON WITH KECCAK- f .........................................................................................................17 | 3.4 COMPARISON WITH KECCAK- f .........................................................................................................17 | | | 4 | SPONGE CONSTRUCTION ............................................................................................................................17 | SPONGE CONSTRUCTION ............................................................................................................................17 | | | 5 | KECCAK.............................................................................................................................................................19 | KECCAK.............................................................................................................................................................19 | | | | 5.1 SPECIFICATION OF pad10*1 .............................................................................................................19 | 5.1 SPECIFICATION OF pad10*1 .............................................................................................................19 | | | | 5.2 SPECIFICATION OF KECCAK[ c ].........................................................................................................20 | 5.2 SPECIFICATION OF KECCAK[ c ].........................................................................................................20 | | | 6 | 6.1 SHA-3 HASH FUNCTIONS ................................................................................................................20 | 6.1 SHA-3 HASH FUNCTIONS ................................................................................................................20 | | | | 6.2 SHA-3 EXTENDABLE-OUTPUT FUNCTIONS .....................................................................................20 | 6.2 SHA-3 EXTENDABLE-OUTPUT FUNCTIONS .....................................................................................20 | | | | 6.3 ALTERNATE DEFINITIONS OF SHA-3 EXTENDABLE-OUTPUT FUNCTIONS .......................................21 | 6.3 ALTERNATE DEFINITIONS OF SHA-3 EXTENDABLE-OUTPUT FUNCTIONS .......................................21 | | | 7 | | | CONFORMANCE..............................................................................................................................................21 | | A | SECURITY.........................................................................................................................................................23 | SECURITY.........................................................................................................................................................23 | | | | A.1 SUMMARY........................................................................................................................................23 A.2 ADDITIONAL CONSIDERATION FOR EXTENDABLE-OUTPUT FUNCTIONS ..........................................24 | A.1 SUMMARY........................................................................................................................................23 A.2 ADDITIONAL CONSIDERATION FOR EXTENDABLE-OUTPUT FUNCTIONS ..........................................24 | |"}], "metadata": {"source": "SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface 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| 2. Overview: Concepts and Constructs................................................................................................3 |\n| 2.3.1."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop provide? (Part 5)"}, {"role": "assistant", "content": "-------------------------------------------------------|\n| 2 | Workshop................................................................................................................\n1 Summary and Key Takeaways..............................................................................4 |\n| | 1.2 About the Cybersecurity Risks in Consumer Home IoT Devices Virtual |\n| 3 | Next Steps ............................................................................................................11 |\n| | References...................................................................................................................12 |\n| List of Appendices | Appendix A-Poll Results .........................................................................................13 |\n| A.1 | Ultimate Demand Driver for Security in Home IoT ........................................ 13 |\n| A.2 | Willingness to Pay More for Security in Low-Cost IoT Devices..................... 14 |\n| A.3 | Primary Responsibility for Home IoT Device Security..................................."}], "metadata": {"source": "Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guidelines on PDA Forensics:\n\n## Guidelines on PDA Forensics\n\n## Guidelines on PDA Forensics\n\nPersonal Digital Assistants (PDAs) are a relatively recent phenomenon, not usually covered in classical computer forensics. This guide attempts to bridge that gap by providing an in-depth look into PDAs and explaining the technologies involved and their relationship to forensic procedures. It covers three families of devices Pocket PC, Palm OS, and Linux-based PDAs - and the characteristics of their associated operating system. This guide also discusses procedures for the preservation, acquisition, examination, analysis, and reporting of digital information present on PDAs, as well as available forensic software tools that support those activities."}], "metadata": {"source": "Guidelines on PDA Forensics", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Vetting the Security of Mobile Applications:\n\nand therefore the simulation may not be completely accurate. Note that malware increasingly detects the use of emulators as a testing platform and changes its behavior accordingly to avoid detection.\nTherefore, it is recommended that test tools use a combination of emulated and physical mobile devices to avoid falsenegatives from malware that employs anti-detection techniques."}], "metadata": {"source": "Vetting the Security of Mobile Applications", "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 Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT):\n\n-  Connected vehicle IoT enables vehicles, roads, and other infrastructure to communicate and share vital transportation information. -  Consumer IoT consists of IoT applications in residences as well as wearable and mobile devices. -  Health IoT processes data derived from sources such as electronic health records and patient-generated health data. -  Smart building IoT includes energy usage monitoring systems, physical access control security systems and lighting control systems. -  Smart manufacturing IoT enables enterprise-wide integration of data, technology, advanced manufacturing capabilities, and cloud and other services. In the above examples, consent provides the core access control attribute needed to authorize disclosure and distribution of protected health information. Emerging healthcare security and messaging standards will enable information classification (labeling) that, with appropriate clearances, will provide interoperable security systems employing attribute-based access control (ABAC) methods. In the IoT, new models of computable healthcare trust may become commonplace. -  Restricting logical access to the network and network activity. This may include using unidirectional gateways, a demilitarized zone network architecture with firewalls to prevent network traffic from passing directly between the corporate and IoT networks, and having separate authentication mechanisms and credentials for users of the corporate and IoT networks. An IoT system should use a network topology that has multiple layers, with each layer's security considered separately, so that all communication occurs with as much security and reliability as afforded by the technology. -  Restricting physical access to IoT network and components. Unauthorized physical access to components could cause serious disruption of an IoT system's functionality. A combination of physical access controls should be used, such as locks, card readers, and/or guards."}], "metadata": {"source": "Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations:\n\n| Cryptographic keying relationship | Two or more entities share the same symmetric key. |\n|--------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Cryptographic Key Management System (CKMS) | The framework and services that provide for the generation, production, establishment, control, accounting, and destruction of cryptographic keys It includes all elements (policies, procedures, devices, and components); facilities; personnel; procedures; standards; and information products that form the system that establishes, manages, and supports cryptographic products and services for end entities. The CKMS may handle symmetric keys, asymmetric keys or both. |\n| Cryptographic mechanism | An element of a cryptographic application, process, module or device that provides a cryptographic service, such as confidentiality, integrity, source authentication, and access control (e.g., encryption and decryption, and digital signature generation and verification). |\n| Cryptographic module | The set of hardware, software, and/or firmware that implements approved cryptographic functions (including key generation) that are contained within the cryptographic boundary of the module. |\n| Cryptographic product | Software, hardware or firmware that includes one or more cryptographic functions. Acryptographic product is or contains a cryptographic module."}], "metadata": {"source": "Recommendation for Key Management_ Part 2 – Best Practices for Key Management 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 Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance:\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\n29 Draft SP 800-118, Guide to Enterprise Password Management , is currently under development [SP 800118]."}], "metadata": {"source": "Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance", "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.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.6 (NIST 3.4.6)?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\n3.4.6 Client Software Selection\n\nAlthough SSL VPNs are described as clientless, some forms of SSL VPN access such as network extension require dynamically downloaded agents to be run on the host."}], "metadata": {"source": "Guide to SSL VPNs", "cmmc_level": "all", "nist_control": "3.4.6", "cmmc_practice_id": "CM.L2-3.4.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Cryptographic Key Generation:\n\n| | pair itself or a trusted party generated the key pair for the entity. 2. For a symmetric key (i.e., a secret key), the entity or entities that are authorized to share and use the key. |\n|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Parameter | Avalue that is used to control the operation of a function or that is used by a function to compute one or more outputs. |\n| Party | See Entity. |\n| Password | A string of characters (letters, numbers, and other symbols) that are used to authenticate an identity or to verify access authorization. A passphrase is a special case of a password that is a sequence of words or other text. In this Recommendation, the use of the term 'password' includes this special case. |\n| Permutation | An ordered (re)arrangement of the elements of a (finite) set; a function that is both a one-to-one and onto mapping of a set to itself. |\n| Plaintext data | In this Recommendation, data that will be encrypted by an encryption algorithm or obtained from ciphertext using a decryption algorithm. |\n| Pre-shared key | A secret key that has been established between the parties who are authorized to use it by means of some secure method (e.g., using a secure manual-distribution process or automated key-establishment scheme)."}], "metadata": {"source": "Recommendation for Cryptographic Key Generation", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.12 (NIST 3.2.12)?"}, {"role": "assistant", "content": "According to Research Report_ User Perceptions of Smart Home Privacy and Security:\n\n3.2.12 | Risk Acceptance | 20 |\n| 3. 3.2.12 Risk Acceptance\n\nAlthough some participants had concerns, they ultimately made a conscious choice, described as 'willful ignorance' by P1\\_A, to accept privacy and security risks in exchange for perceived benefits."}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "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 Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe predominant application architecture for cloud-native applications consists of multiple microservices, accompanied in some instances by a centralized application infrastructure, such as a service mesh, that provides all application services. This class of applications is generally developed using a flexible and agile software development paradigm called DevSecOps. A salient feature of this paradigm is the use of flow processes called continuous integration and continuous deployment (CI/CD) pipelines, which initially take the software through various stages (e.g., build, test, package, and deploy) in the form of source code through operations that constitute the software supply chain (SSC) in order to deliver a new version of software . This document outlines strategies for integrating SSC security measures into CI/CD pipelines.\n\nactor; artifact; attestation; CI/CD pipeline; package; provenance; repository; SBOM; SDLC; SLSA; software supply chain."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Cryptographic Algorithms and Key Sizes for Personal Identity Verification:\n\nSpecification of Digital Signatures on Authentication Information..........................................7 | 3.2.1. Specification of Digital Signatures on Authentication Information..........................................7 | |\n| | 3.2.2. Specification of Public Keys In X.509 Certificates .....................................................................8 | 3.2.2. Specification of Public Keys In X.509 Certificates .....................................................................8 | |\n| | 3.2.3."}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 3)"}, {"role": "assistant", "content": "efore the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review draft publications during the public comment periods and provide feedback to NIST. Many NIST publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sec-cert@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA) [FOIA96]. \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Reports on Computer Systems Technology\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters:\n\n3.2.2 | 3. 3.2.2 Voter Authentication\n\nState law will determine appropriate authentication mechanisms for accepting voter registration materials, blank ballot requests, and returned marked ballots."}], "metadata": {"source": "Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters", "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 Glossary of Computer Security Terminology provide? (Part 2)"}, {"role": "assistant", "content": "ic dissemination of this federally sponsored work. This publication is part of a continuing effort to assist federal agencies in accordance with NIST's mandate under the Computer Security Act of 1987.\nNIST expresses its appreciation to the Subcommittee on Information Systems Security (SISS) and the Executive Secretariat of the National Security Telecommunications and Information Systems Security Committee for their kind permission to publish this report. We also wish to acknowledge the many computer security professionals who participated in the development of this glossary. Questions regarding this publication should be addressed to the Associate Director for Computer Security, Computer Systems Laboratory, Building 225, Room B154, National Institute of Standards and Technology, Gaithersburg, MD, 20899. Additional copies of this publication may be purchased through the National Technical Information Service, Springfield, VA, 22161, telephone: (703) 487-4650. ## Glossary of Computer Security Terminology\n\n## -A-\n\n| aborted connection | Disconnection which does not follow established procedures. This may occasionally result from a bad phone connection, but more typically results when the user \"hangs up\" without attempting to issue the disconnect commands. Note: Some systems are sensitiue to aborted connections, and do not detect the disconnect and reset for the next user. Continued aborts are considered [improper], and may result in a warning or revocation of access privileges."}], "metadata": {"source": "Glossary of Computer Security Terminology", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\n| . | . | . . | III-17 |\n| III-13 | Physical/Environmental Protection-GADPS | | . | . | .\n| III-17 |\n| III-14 | Controls-GADPS | | | | | III-17 |\n| III-15 | Production, I/O Emergency, Backup, and Cont. Planning-GADPS | | | | | III-18 |\n| III-16 | Software and Maintenance-GADPS | . | . | . | . | III-18 |\n| III-17 | System Security Awareness and Training-GADPS | . | . | . | . | III-18 |\n| III-18 III-19 | Authorization and Access Controls-GADPS Audit Trail Mechanisms-GADPS | | . . | . . | . . | III-19 III-19 |\n| III-20 | Confidentiality Controls-GADPS | | | | | III-19 |\n| III-21 | Integrity Controls-GADPS | | | | | III-20 |\n| III-22 | User | Identification/Authorization-GADPS | . | . | . | III-20 |\n| III-23 | Assignment Security Responsibility-MAS | | | . | . | III-22 |\n| III-24 | Personnel Screening-MAS . | . | | . | ."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Application Whitelisting provide? (Part 3)"}, {"role": "assistant", "content": "blic 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\nAn application whitelist is a list of applications and application components that are authorized for use in an organization. Application whitelisting technologies use whitelists to control which applications are permitted to execute on a host. This helps to stop the execution of malware, unlicensed software, and other unauthorized software. This publication is intended to assist organizations in understanding the basics of application whitelisting. It also explains planning and implementation for whitelisting technologies throughout the security deployment lifecycle."}], "metadata": {"source": "Guide to Application Whitelisting", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Understanding Stablecoin Technology and Related Security Considerations:\n\nAll such issued stablecoins are over-collateralized, which promotes the maintenance of the stablecoin peg since stablecoins can always be redeemed from the issuer at their pegged price. The price is further stabilized through arbitrage. If the price of the stablecoin on third-party markets falls below its peg, then borrowers of the stablecoin can purchase the stablecoin at a discount price and use it to pay off their debt positions (making a profit). When debt positions are paid off, the provided stablecoins are burned. This reduces the overall supply, which puts an upward pressure on the price. If the price of the stablecoin on third-party markets rises above its peg, then borrowers will take on additional debt positions, which results in the minting of additional stablecoins. The borrowers can then immediately sell the newly minted stablecoins on third-party markets for a profit. This increases the overall supply, which puts a downward pressure on the price. The cryptocurrency-backed stablecoins minted through loan issuance (Section 4.2) require users to post cryptocurrency as collateral when borrowing. This mitigates the cryptocurrency losing its price peg since enough collateral should be maintained to cover all issued stablecoins. However, since the posted collateral is in the form of cryptocurrency, it may be extremely volatile. Thus, borrowers are required to over-collateralize. When borrowing, the stablecoin system will specify a minimum required collateral ratio. That is, the user must maintain a certain value of cryptocurrency collateral to cover the price of the borrowed stablecoins. If the user falls below that ratio (through the posted cryptocurrency losing value), then the user is required to post more collateral, or their collateral may be subject to liquidation. This is very similar to the maintenance of margin loans in the stock market. Margin investors in the stock market may be required to post additional collateral to cover stock market loses."}], "metadata": {"source": "Understanding Stablecoin Technology and Related Security Considerations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Incident Response?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2:\n\ntions from SCAP 1.1: XCCDF from 1.1.4 to 1.2; OVAL from 5.8 to 5.10; and CPE from 2.2 to 2.3. Added and revised requirements throughout the specification to use these component specification versions.\n-  In Section 2, rewrote the conformance requirements and defined 'content producer' and 'content consumer' terms. -  Section 3:\n- o Added an SCAP source data stream subsection and a subsection on digitally signing source data stream content. - o Added identifier use requirements for <xccdf:Rule> and <xccdf:ident > elements. - o Added requirements for the <xccdf:Value> element. - o Added requirements related to Schematron rules. -  Section 4:\n- o Revised legacy support requirements for SCAP content and OVAL definition documents. - o Added an SCAP result data stream subsection. Added source and result data stream requirements throughout the section. Also added a subsection on digitally signing result data stream content. - o Added a declaration of the FDCC Reporting Format. -  In Section 5, added malware detection material to the Inventory Scanning use case. -  Updated the normative references. -  Added Appendix C (change log)."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\n3.1.1 | Identification | 3-1 |\n| | | 3. 3.1.1 Identification\n\nA userlD represents a user uniquely."}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating Systems", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2011 Annual Report:\n\n| Research in Emerging Technologies ..........................................34 | |\n|---------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|\n| Automated Combinatorial Testing for Software .................................. | 34 |\n| Cloud Computing and Virtualization................................................ | 35 |\n| Security Ontologies for Risk Assessment........................................... | 36 |\n| Mobile Device Security | ............................................................... 36 |\n| Access Control and Privilege Management | .................................37 |\n| Access Control and Privilege Management Research............................. | 37 |\n| Conformance Verification for Access Control Policies ........................... | 38 |\n| Metrics for Evaluation of Access Control Systems................................ | 38 |\n| Policy Machine ........................................................................."}], "metadata": {"source": "Computer Security Division 2011 Annual Report", "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 Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\n| 1 | | | Scope..............................................................................................................................2 | | | | Audience | .........................................................................................................................5 | | Intended Use..........................................................................................................................6 | Intended Use..........................................................................................................................6 | Intended Use..........................................................................................................................6 | | | Overview ................................................................................................................................7 | Overview ................................................................................................................................7 | | | Risk Management Overview..........................................................................................."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh:\n\n- Multiple, loosely coupled microservices communicate through network calls, and these communication links must be protected. In the case of monolithic applications, these communications take place through procedure calls.\n- The entire network and all microservices are untrusted. Therefore, mutual authentication and secure communication channels between microservices through mechanisms such as mutual Transport Layer Security (TLS) (mTLS) are required.\n- The logging data that pertains to each microservice must be consolidated to obtain a security profile in order for forensics, audits, and analytics to assess the overall health of the application.\n\n- The proxies (e.g., Ingress, sidecar, and Egress) play the role of PEPs since they intercept all requests that emanate from each client, user, service, or external service.\n- The PEPs enforce access control policies by performing the allow/deny actions based on the verdict provided by PDP.\n- The enforcement function can be provided either natively (using local configuration structures, such as Access Control Lists [ACLs]) or using proxy extensions that call an external authorization server to obtain one or more of the data in the previous bullet.\n- The assurance mechanisms in the service mesh (e.g., certificate-based authentication, secure session, non-bypassability, execution isolation) can be leveraged to deploy a high assurance authorization framework. Execution isolation is running each software component in a contained environment or sandbox-leveraging hardware virtualization that limits the damage of malware, limits the speed and propagation of worms and viruses, and efficiently detects attacks."}], "metadata": {"source": "Attribute-based Access Control for Microservices-based Applications using a Service Mesh", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) provide? (Part 5)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| | Introduction ...........................................................................................................................1 | Introduction ...........................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| | Purpose and Objectives.................................................................................................."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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_ Federation and Assertions:\n\n|\n| | 2.4. | Federation Assurance Level 3 (FAL3) . . . . . . . . . . . . . . . . . . . . 7 |\n| 2.5.\n| Requesting and Processing xALs . . . | . . . . . . . . . . . . . . . . . . . 8 |\n| 3. Common Federation Requirements . . . . . . . . . . . . . . . . . . . . . . . 10 | 3. Common Federation Requirements . . . . . . . . . . . . . . . . . . . . . . . 10 | 3. Common Federation Requirements . . . . . . . . . . . . . . . . . . . . . . . 10 |\n| 3.1. | | Federation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 |\n| 3.2. | | Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 |\n| | 3.2.1. | Credential Service Provider (CSP) . . . . . . . . . . . . . . . . . 12 |\n| | 3.2.2. . . | Identity Provider (IdP) . . . . . . . . . . . . . . . . . . . . . 12 |\n| | 3.2.3. | Relying Party (RP) . . . . . . . . . . . . . . . . . . . . . . . . . 13 |\n| 3.3. | Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 | Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 |\n| | 3.3.1. | Trust Agreement Management . . . . . . . . . . . . . . . . . . 13 |\n| | 3.3.2. ."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Information Security Handbook_ A Guide for Managers:\n\n| 1. Introduction .................................................................................................... | 1. Introduction .................................................................................................... | 1. Introduction .................................................................................................... | 1. Introduction ...................................................................................................."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\n| | Introduction ...........................................................................................................................1 | Introduction ...........................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| | Purpose and Objectives.................................................................................................."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Practical Combinatorial Testing:\n\n| CONFIGURATION TESTING ...................................................................."}], "metadata": {"source": "Practical Combinatorial Testing", "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 Approaches for Federal Agencies to Use the Cybersecurity Framework:\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. Agencies often track managed vulnerabilities, vulnerability mitigation plans, and accepted vulnerabilities on a system-by-system basis. This information is in the system Security Authorization Package, which includes the system security plan (SSP), the security assessment report (SAR), and the plan of action and milestones (POA&Ms)."}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "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 Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities provide? (Part 5)"}, {"role": "assistant", "content": "| Establishing a Test, Training, and Exercise Program | | | | | 2.1 | Develop Comprehensive TT&E Policy.....................................................................2-3 | | | | 2.2 | Identify TT&E Roles and Responsibilities ................................................................2-4 | | | | 2.3 2.4 | Establish Overall TT&E Schedule............................................................................2-4 Document TT&E Event Methodology.......................................................................2-4 | | | | 2.5 | Recommendations...................................................................................................2-5 | | | 3."}], "metadata": {"source": "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Discussion on the Full Entropy Assumption of the SP 800-90 Series 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. ## 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\n\n## How to Cite this NIST Technical Series Publication:\n\nBuller D, Kaufer A, Roginsky A, Sönmez Turan M (2023) Discussion on the Full Entropy Assumption of the SP 800-90 Series. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8427. https://doi.org/10.6028/NIST.IR.8427\n\n## Author ORCID iDs\n\nRoginsky, Allen: 0000-0003-2684-6736 Meltem Sönmez Turan: 0000-0002-1950-7130\n\n## Submit Comments\n\nrbg\\_comments@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe NIST Special Publication (SP) 800-90 series supports the generation of high-quality random bits for cryptographic and non-cryptographic use. The security strength of a random number generator depends on the unpredictability of its outputs. This unpredictability can be measured in terms of entropy, which the NIST SP 800-90 series measures using min-entropy . A full-entropy bitstring has an amount of entropy equal to its length. Full-entropy bitstrings are important for cryptographic applications, as these bitstrings have ideal randomness properties and may be used for any cryptographic purpose."}], "metadata": {"source": "Discussion on the Full Entropy Assumption of the SP 800-90 Series", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Practical Combinatorial Testing:\n\n| 1 INTRODUCTION .........................................................................................2 | 1 INTRODUCTION .........................................................................................2 | 1 INTRODUCTION .........................................................................................2 | | |-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| | 1.1 | 1.1 | Authority..............................................................................................................2 | | | 1.2 | 1.2 | Document Scope and Purpose | .............................................................................2 | | 1.3 | 1.3 | Audience and Assumptions..................................................................................3 | | | 1.4 | 1.4 | Organization: How to use this Document...........................................................3 | | | 2 COMBINATORIAL METHODSIN TESTING.................................................4 | 2 COMBINATORIAL METHODSIN TESTING.................................................4 | 2 COMBINATORIAL METHODSIN TESTING.................................................4 | | | 2.1 | 2.1 | Two Forms of Combinatorial Testing..................................................................6 | | | 2.2 | 2.2 | The Test Oracle Problem | .....................................................................................9 | | 2.3 | 2.3 | Chapter Summary | ..............................................................................................10 | | 3 | CONFIGURATION TESTING ...................................................................."}], "metadata": {"source": "Practical Combinatorial Testing", "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 Secure Deployment of IPv6:\n\nAnother limitation of IPv4 is that its design favored interoperability over security and did not contain features that protected the confidentiality, integrity, or availability of communications. For example, IPv4 could not cryptographically protect data from eavesdropping or manipulation, and IPv4 did not provide a method for endpoints to authenticate each other. Over time, the open nature of IPv4 was increasingly a target of exploitation. The multi-path nature of the Internet, which was designed for high availability, also allows multiple attack vectors for a variety of threats. As a response, new technologies were added to IPv4 to provide needed security functionality. With IPv6, these features were designed into the new protocol as mandatory components. IP security (IPsec) is a suite of protocols for securing Internet Protocol (IP) communications by authenticating the sender and providing integrity protection plus optionally confidentiality for the transmitted data. This is accomplished through the use of two extension headers: the Encapsulating Security Payload (ESP) and the Authentication Header (AH). The negotiation and management of IPsec security protections and the associated secret keys is handled by the Internet Key Exchange (IKE) protocol. IPsec is a mandatory part of an IPv6 implementation; however, its use is not required. IPsec is also specified for securing particular IPv6 protocols (e.g., Mobile IPv6 and OSPFv3 [Open Shortest Path First version 3]). Section 5.3 describes IPsec in detail. -  Routing Header . NH value of 43 in the immediately preceding header. The Routing Header is used by an IPv6 source (sending host) to list one or more intermediate nodes to be traversed on the way to a packet's destination. The sending host sets the NH extension to direct a packet through a certain path. In IPv4, this is called the Loose Source and Record Route option."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "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 Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\n| Executive Summary............................................................................................................................1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. Cybersecurity Risk Considerations ..................................................................................................9 |\n| 2.2.1. Factors Influencing Prioritization ................................................................................................12 |\n| 2.2.2. Cybersecurity Risk Optimization .................................................................................................12 |\n| 2.2.3. Cybersecurity Risk Priorities at Each Enterprise Level................................................................14 |\n| 2.2.4. Considerations of Positive Risks as an Input to ERM..................................................................15 |\n| 2.2.5. Visualizing Risk Priority ...............................................................................................................16 |\n| 2.3.1. Risk Acceptance...........................................................................................................................21 |\n| 2.3.2. Risk Avoidance ............................................................................................................................22 |\n| 2.3.3. Risk Transfer................................................................................................................................22 |\n| 2.3.4."}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-07-25\n\n## How to Cite this NIST Technical Series Publication\n\nBooth H, Souppaya M, Vassilev A, Ogata M, Stanley M, Scarfone K (2024) Secure Development Practices for Generative AI and Dual-Use Foundation AI Models: An SSDF Community Profile. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-218A. https://doi.org/10.6028/NIST.SP.800-218A\n\n## Author ORCID iDs\n\nHarold Booth: 0000-0003-0373-6219 Murugiah Souppaya: 0000-0002-8055-8527 Apostol Vassilev: 0000-0002-9081-3042 Michael Ogata: 0000-0002-8457-2430 Karen Scarfone: 0000-0001-6334-9486\n\n## Contact Information\n\nssdf@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/218/a/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis document augments the secure software development practices and tasks defined in Secure Software Development Framework (SSDF) version 1.1 by adding practices, tasks, recommendations, considerations, notes, and informative references that are specific to AI model development throughout the software development life cycle."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Module-Lattice-Based Digital Signature Standard:\n\n1. Name of Standard. Module-Lattice-Based Digital Signature Standard (FIPS 204). 2. Category of Standard. Computer Security. Subcategory. Cryptography. 3. Explanation. This standard specifies ML-DSA, a lattice-based digital signature algorithm for applications that require a digital signature rather than a written signature. Additional digital signature schemes are specified and approved in other NIST Special Publications and FIPS publications (e.g., FIPS 186-5 [1]). A digital signature is represented in a computer as a string of bits and computed using a set of rules and parameters that allow the identity of the signatory and the integrity of the data to be verified. Digital signatures may be generated on both stored and transmitted data. 7. Applications. A digital signature algorithm allows an entity to authenticate the integrity of signed data and the identity of the signatory. The recipient of a signed message can use a digital signature as evidence in demonstrating to a third party that the signature was, in fact, generated by the claimed signatory. This is known as non-repudiation since the signatory cannot easily repudiate the signature at a later time. A digital signature algorithm is intended for use in electronic mail, electronic funds transfer, electronic data interchange, software distribution, data storage, and other applications that require data integrity assurance and data origin authentication. 8. Implementations. A digital signature algorithm may be implemented in software, firmware, hardware, or any combination thereof. NIST will develop a validation program to test implementations for conformance to the algorithm in this standard. For every computational procedure that is specified in this standard, a conforming implementation may replace the given set of steps with any mathematically equivalent set of steps. In other words, different procedures that produce the correct output for every input are permitted."}], "metadata": {"source": "Module-Lattice-Based Digital Signature Standard", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to Protecting the Confidentiality of Personally Identifiable Information (PII):\n\nThe primary audience for this document is the individuals who apply policies and procedures for protecting the confidentiality of PII on Federal information systems, as well as technical and nontechnical personnel involved with implementing system-level changes concerning PII protection methods. Individuals in many roles should find this document useful, including chief privacy officers and other privacy officers, privacy advocates, privacy support staff, public affairs staff, compliance officers, human resources staff, system administrators, chief information security officers, information system security officers, information security support staff, computer security incident response teams, and chief information officers.\n\npersonnel when investigating incidents. All access to the log occurs only from the organization's own systems.\n\nManagement of incidents involving PII often requires close coordination among personnel from across the organization, such as the CIO, CPO, system owner, data owner, legal counsel, and public relations officer. Because of this need for close coordination, organizations should establish clear roles and responsibilities to ensure effective management when an incident occurs."}], "metadata": {"source": "Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to U.S. Department of Justice Simplified Risk Analysis Guidelines:\n\n- 3.3. Application Systems.\n- a. Nonsensitive.\n- (1) A management control process shall be established to assure that appropriate administrative, physical, and technical safeguards are incorporated into all new applications, and into significant modifications to existing applications.\n- (2) The AIS shall control the capability to input, update, or change system data and restrict this capability to specified authorized individuals or groups\n- (3) Security measures to validate data must be implemented.\n- (4) All system users shall be uniquely identified and\n- authenticated\n- b. Sensitive. In addition to the requirements for nonsensitive application systems listed above, the minimum security requirements listed below for sensitive application systems must be met.\n- (1) Security requirements and specifications must be defined and approved by the application system manager prior to acquiring or starting formal development of the application. Prior to placing the application in operation, design reviews and system tests shall be conducted to assure that the proposed design meets the security specifications.\n- (2) Upon completion of the system tests, the application system manager must certify that the system meets all applicable Federal policies, regulations, and standards, and that the results of the tests demonstrate that the installed security safeguards are adequate for the application.\n- (3) Contingency plans must be developed to assure that users can continue to perform essential functions in the event their data processing support is interrupted. The plans should be consistent with the contingency plans of the AIS installation that is processing the application."}], "metadata": {"source": "U.S. Department of Justice Simplified Risk Analysis Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation:\n\n-------------------------------------------------------------------------------------------------|\n| [Murphy] | S. Murphy, 'RPKI Tutorial: Routing Security and RPKI', NANOG on the Road (NOTR), St.\nLouis, MO, November, 2015 https://www.nanog.org/sites/default/files/04-Murphy-StLouis.pdf |\n| [NABCOP] | 'DDoS-DoS-attack-BCOP,' North American BCOP, http://nabcop.org/index.php/DDoS-DoS-attack-BCOP |\n| [Naik] | A. Naik, 'Internet Vulnerability Takes Down Google,' ThousandEyes report, November 2018 . https://blog.thousandeyes.com/internet- vulnerability-takes-down-google/ |\n| [NANOG] | 'Practical BGP Origin Validation using RPKI: Vendor Support, Signing and Validation Services, and Operational Experience,' NANOG Track (multiple presentations) at NANOG 67, Chicago, IL, June 2016 . https://archive.nanog.org/meetings/nanog67/agenda |\n| [NANOG-list] | 'Intra-AS messaging for route leak prevention,' NANOG Email List - Discussion Thread, June 2016. http://mailman.nanog.org/pipermail/nanog/2016-June/thread.html#86348 |\n| [NCCoE-sidr] | W. Haag, D. Montgomery, W.C. Barker, A. Tan, 'Protecting the Integrity of Internet Routing: Border Gateway Protocol (BGP) Route Origin Validation, Volume B,' NIST Special Publication (SP) 1800-14B, August 2018."}], "metadata": {"source": "Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Computer Security Log Management:\n\nchecking software, run periodically instead of continuously, so they generate log entries in batches instead of on an ongoing basis. 4\n- GLYPH<c=31,font=/APONEK+Webdings> Remote Access Software.\nRemote access is often granted and secured through virtual private networking (VPN). VPN systems typically log successful and failed login attempts, as well as the dates and times each user connected and disconnected, and the amount of data sent and received in each user session. VPN systems that support granular access control, such as many Secure Sockets Layer (SSL) VPNs, may log detailed information about the use of resources. - GLYPH<c=31,font=/APONEK+Webdings> Web Proxies. Web proxies are intermediate hosts through which Web sites are accessed. Web proxies make Web page requests on behalf of users, and they cache copies of retrieved Web pages to make additional accesses to those pages more efficient. Web proxies can also be used to restrict Web access and to add a layer of protection between Web clients and Web servers. Web proxies often keep a record of all URLs accessed through them. - GLYPH<c=31,font=/APONEK+Webdings> Vulnerability Management Software. Vulnerability management software, which includes patch management software and vulnerability assessment software, typically logs the patch installation history and vulnerability status of each host, which includes known vulnerabilities and missing software updates. 5 Vulnerability management software may also record additional information about hosts' configurations. Vulnerability management software typically runs occasionally, not continuously, and is likely to generate large batches of log entries. - GLYPH<c=31,font=/APONEK+Webdings> Authentication Servers. Authentication servers, including directory servers and single sign-on servers, typically log each authentication attempt, including its origin, username, success or failure, and date and time."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management:\n\n. To support the development of an Enterprise Risk Register, this report describes documentation of various scenarios based on the potential impact of threats and vulnerabilities on enterprise assets.\nDocumenting the likelihood and impact of various threat events through cybersecurity risk registers integrated into an enterprise risk profile helps to later prioritize and communicate enterprise cybersecurity risk response and monitoring."}], "metadata": {"source": "Identifying and Estimating Cybersecurity Risk for Enterprise Risk 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 Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n) 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."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "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 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\n- 1) The civilian agency CSPPs basically conformed with the guidance given by OMB Bulletin 88-16. Many controls to protect sensitive systems were already in place or planned. These controls appeared consistent with identified system functions, environment, and security needs. However, some respondents appeared to have just \"checked the boxes,\" perhaps presenting a falsely optimistic picture. - 2) Many agencies appeared to report on isolated systems rather than all systems subject to the Computer Security Act and OMB Bulletin 88-16. - 3) Agencywide guidance on how to prepare the plans was not clear. There was also some question whether a high level official reviewed the plans. Also unclear is the distribution of agency-level computer security policy and guidance. Further, most plans did not reflect the joint involvement of ADP, computer security, and applications communities in computer security planning. - 4) Significantly, the plans rarely addressed the security concerns on networking, interfaces with other systems, and the use of contractors and their facilities. This may reflect a general confusion about the boundaries and limits of responsibility for a given system. - 5) Many plans equated sensitivity only with privacy or confidentiality, and did not fully address requirements for integrity and availability. - 1) Agency management should ensure that computer security has the highest level of management involvement. This involvement is also important in the computer security planning process. Computer security benefits from the multiple perspectives of and input from agency IRM, computer security, and functional, user, and applications personnel\n- 2) Agency management should identify and describe the security needs of their systems which contain sensitive information. - 3) Agency management should recognize the importance of computer security and its required planning."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "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 2016 NIST_ITL Cybersecurity Program Annual Report provide? (Part 3)"}, {"role": "assistant", "content": "ld like to thank their ITL colleagues who provided writeups on their 2016 project highlights and accomplishments for this annual report (their names are mentioned after each project writeup).\nThe editors would also like to acknowledge Elaine Barker (CSD), Lisa Carnahan (Standards Coordination Office, NIST), Greg Witte and Larry Feldman (G2) for reviewing and providing valuable feedback for this annual report. The editors would also like to acknowledge Kristen Dill of Dill and Company, Inc. for designing the cover and inside layout for this 2016 annual report. \n\nAny mention of commercial products or organizations is for informational purposes only; it is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the products identified are necessarily the best available for the purpose. \n\nAll names are trademarks or registered trademarks of their respective owners."}], "metadata": {"source": "2016 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Recommendation for Random Bit Generator (RBG) Constructions:\n\n......................21 |\n| 2.8.3.1. Instantiating a DRBG Within an RBG3 Construction.............................................................21 |\n| 2.8.3.2.\nGeneration Using an RBG3 Construction..............................................................................23 |\n| 3. Accessing Entropy Source Output |\n| .................................................................................................26 |\n| 3.2.1.1. Keys Used in External Conditioning Functions......................................................................29 |\n| 3.2.1.2. Hash Function-Based Conditioning Functions......................................................................30 |\n| 3.2.1.3. Block Cipher-Based Conditioning Functions.........................................................................30 |\n| 3.2.2. Using a Vetted Conditioning Function........................................................................................31 |\n| 3.2.2.1. External Conditioning When Full Entropy is Not Required...................................................31 |\n| 3.2.2.2. Conditioning Function to Obtain Full-Entropy Bitstrings......................................................33 |"}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "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 Physical Protection?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. Computing devices that integrate physical and/or sensing capabilities and network interface capabilities are being designed, developed, and deployed at an ever-increasing pace. These devices are fulfilling customer needs in all sectors of the economy. Many of these computing devices are connected to the internet. A novel characteristic of these devices is the combination of connectivity and the ability to sense and/or affect the physical world. As devices become smaller and more complex, with an increasing number of features, the security of those devices also becomes more complex. This publication defines a baseline set of device cybersecurity capabilities that organizations should consider when confronting the challenge of the Internet of Things (IoT)."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Information Security Handbook_ A Guide for Managers:\n\n| |------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| | | Purpose | and Applicability............................................................................................1 | | | | | Relationship to Existing Guidance...............................................................................1 | | | | | Audience .....................................................................................................................1 | | | 2."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Computer Security Training & Awareness Course Compendium:\n\n## Computer Security Training & Awareness Course Compendium\n\n## Computer Security Training & Awareness Course Compendium\n\nThis National Institute of Standards and Technology (NIST) Interagency Report (NISTIR) is a compendium of computer security training and awareness courses. The purpose of this publication is to assist federal agencies locate computer security training resources. This publication is part of a continuing NIST effort to support federal agencies in accordance with NIST's mandate under the Computer Security Act of 1987. In addition to the table of contents, which lists the courses, there are four appendices: A) lists the courses by training areas within audience categories as defined in NIST Special Publication 500-172, Computer Security Training Guidelines: B) lists the vendors that participated in this effort; C) lists the specific products for which training is available; and D) lists the product specific courses."}], "metadata": {"source": "Computer Security Training & Awareness Course Compendium", "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 Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\nType.............................................................98 | | | C.3.5.8 System and Network Monitoring Information Type...............................................100 | | | C.3.5.9 Information Sharing Information Type...................................................................101 | | | APPENDIX D: IMPACT DETERMINATION FOR MISSION-BASED INFORMATION AND INFORMATION SYSTEMS......................................................102 | | | D.2 Homeland Security.............................................................................................................."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography provide? (Part 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1 provide? (Part 4)"}, {"role": "assistant", "content": "-------------------------------------------------------|\n| 1. Introduction ........................................................................................................................ | 1.\nIntroduction ........................................................................................................................ | 1. Introduction ........................................................................................................................"}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Threat Assessment of Malicious Code and External Attacks:\n\n3.4.1 | Configuration Errors and Passwords | 13 |\n| | | 3. 3.4.1 Configuration Errors and Passwords\n\nToday, desktop workstations are becoming the tool of more and more scientists and professionals."}], "metadata": {"source": "Threat Assessment of Malicious Code and External Attacks", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities provide? (Part 3)"}, {"role": "assistant", "content": "l Institute of Standards and Technology would also like to express its appreciation and thanks to the Department of Homeland Security for its sponsorship and support of NIST Special Publication 80084.\n## Table of Contents\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\n5 AU-4, CP- 2, SC-5 | Double extortion - demanding payment both to restore data access and to not sell or publish the data elsewhere - is common, so data leak prevention solutions are important. |\n| | PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity ISO/IEC 27001:2013 A.12.2.1, A.12.5.1, A.14.1.2, A.14.1.3, A.14.2.4 NIST SP 800-53 Rev. 5 SC-16, SI- | Integrity checking mechanisms can detect tampered software updates that can be used to insert malware that enables ransomware events. |\n| | PR.DS-7: The development and testing environment(s) are separate from the production environment ISO/IEC 27001:2013 A.12.1.4 NIST SP 800-53 Rev."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n| 5.6.1.2.2 Key Pair Generation by Testing Candidates........................\n| 31 |\n| 5.6.2 Required Assurances.......................................................................................... | 5.6.2 Required Assurances.......................................................................................... | 32 |\n| 5.6.2.1 | Assurances Required by the Key Pair Owner..................................... | 33 |\n| | 5.6.2.1.1 Owner Assurance of Correct Generation............................. | 35 |\n| | 5.6.2.1.2 Owner Assurance of Private-Key Validity .......................... | 35 |\n| | 5.6.2.1.3 Owner Assurance of Public-Key Validity ........................... | 36 |\n| | 5.6.2.1.4 Owner Assurance of Pair-wise Consistency........................ | 36 |\n| | 5.6.2.1.5 Owner Assurance of Possession of the Private Key............ | 37 |\n| 5.6.2.2 | Assurances Required by a Public Key Recipient................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities:\n\n3.3.2 Collateral Damage Potential (CDP)\n\nThe Collateral Damage Potential metric measures the potential for loss of life or physical assets through damage or theft of property or equipment."}], "metadata": {"source": "The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Secure Domain Name System (DNS) Deployment Guide:\n\n7-1 | |------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------| | 7.1 Securing DNS Host Platform ..................................................................................7-1 | 7.1 Securing DNS Host Platform ..................................................................................7-1 | 7.1 Securing DNS Host Platform ..................................................................................7-1 | | | 7.2 Securing DNS Software..........................................................................................7-1 | 7.2 Securing DNS Software..........................................................................................7-1 | 7.2 Securing DNS Software..........................................................................................7-1 | | | | 7.2.1 | Running the Latest Version of Name Server Software ..............................."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment 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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Annual Report 2018_ NIST_ITL Cybersecurity Program:\n\n- Release of the first update of the Framework for Improving Critical Infrastructure Cybersecurity , popularly known as simply the 'Cybersecurity Framework.' First produced in February 2014 with the active involvement of hundreds of organizations in the private and public sectors, Version 1.1 was released in April 2018. Based on the experience of Framework users and changes in the cybersecurity environment and technological advances, the revision added more content related to supply chain risk management and coordinated vulnerability disclosure. NIST added and clarified language regarding cybersecurity measurement with an emphasis on self-assessment. The number of downloads of Version 1.1 has far surpassed that of the initial version. - Better preparing an organization's senior leaders to execute the RMF, as well as how to communicate their protection plans and risk management strategies to system implementers and operators. - Incorporating supply chain risk management considerations . The RMF now addresses growing supply chain concerns, such as counterfeit components, tampering, theft, insertion of malicious software and hardware, poor manufacturing and development practices, and other potentially harmful activities that can impact an organization's systems and systems components. - Supporting security and privacy safeguards . The RMF update provides organizations with a disciplined and structured process to select controls from the newly developed consolidated security and privacy control catalog in NIST's SP 800-53 Revision 5. 7 This should be valuable to companies and organizations beyond the federal government, considering how high profile the subject of privacy has become as of late. - Roots of Trust . Modern computing devices consist of varied hardware, firmware, and software components at multiple layers of abstraction."}], "metadata": {"source": "Annual Report 2018_ NIST_ITL Cybersecurity Program", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Security for Full Virtualization Technologies provide? (Part 5)"}, {"role": "assistant", "content": "1-1 | | | 1.1 | Authority.................................................................................................................1-1 | | | | 1.2 | Purpose and Scope................................................................................................1-1 | | | | 1.3 | Audience ................................................................................................................1-1 | | | | 1.4 | Document Structure ...............................................................................................1-1 | | | 2."}], "metadata": {"source": "Guide to Security for Full Virtualization Technologies", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Standard Security Label for GOSIP_ an Invitational Workshop:\n\n3.5.3 In terms of labelling, this model would require that an object refer to label components addressing classification and designation."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Security Assessment?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\nWhile some ideas for means of addressing these challenges came up during discussions, all need further evaluation to identify the right mix of technical capabilities, manufacturer support, and public education to address."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\n3.1.6 Verify contents of signerInfos\n\n| Purpose | Confirms that the signerInfos in the SignedData is populated with a single SignerInfo. 3.1.6: Verify contents of signerInfos | The tester shall validate that only a single SignerInfo exists in the SignedData."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to ISCMA_ An Information Security Continuous Monitoring Program Assessment:\n\n65 | References....................................................................................................................... 65 | References......................................................................................................................."}], "metadata": {"source": "ISCMA_ An Information Security Continuous Monitoring Program Assessment", "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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Hardware Security Failure Scenarios_ Potential Hardware Weaknesses:\n\n1. An attacker with physical access to a chip can leverage a lack of or faults in debug/test interface access control to read and set registers (e.g., via a scan chain using a Joint Test Action Group [JTAG] interface) and bypass normal on-chip protections [CWE-1191]. 2. Malicious code on a device may leverage a lack of granularity in hardware access control to read or modify assets (e.g., device configuration and keys) by taking advantage of unintended privileges [CWE-1220]. 3. New functionality may not be implementable because a programmable lock bit set during the boot process prevents an unnecessarily large address region from being written [CWE-1222]. 4. Malicious code can take advantage of an improper implementation of write-once register bits to reprogram system settings (e.g., boot time configuration) [CWE-1224]. 5. Attackers may unlock a secured system by leveraging design or code errors to modify trusted lock bits that should have their values immutable after the initial set, thereby enabling writes to protected registers or address regions [CWE-1231]. 6. Attackers can gain full read-write access to a device by accessing undocumented features (typically put there to allow for easy developer testing) that circumvent security controls. These are often implemented as 'chicken bits' - undocumented bits that disable security features [CWE-1242]. 7. Attackers can write malicious code to memory and then execute it because the central processing unit (CPU) does not support a bit that defines read-only and write-only regions of memory. This can also happen if the CPU relies on an improperly configured memory protection unit (MPU) and memory management unit (MMU) for read and write exclusivity [CWE-1252]. 8. Attackers can access protected memory regions and perform both read and write by using memory alias addresses (i.e., redundant addresses that point to the same memory region) or mirrored memory regions that do not have the same protections."}], "metadata": {"source": "Hardware Security Failure Scenarios_ Potential Hardware Weaknesses", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance provide? (Part 3)"}, {"role": "assistant", "content": "sured network, device, and operational performance impacts for a process-based manufacturing environment (Volume 2) and a discrete-based manufacturing environment (Volume 3) are included in the guide.\nManufacturers should make their own determinations about the breadth of the proof-of-concept solutions they voluntarily implement. Some important factors to consider include: company size, cybersecurity expertise, risk tolerance, and the threat landscape. The CSF Manufacturing Profile can be used as a roadmap for managing cybersecurity risk for manufacturers and is aligned with manufacturing sector goals and industry best practices. The Manufacturing Profile provides a voluntary, risk-based approach for managing cybersecurity activities and cyber risk to manufacturing systems. The Manufacturing Profile is meant to complement but not replace current cybersecurity standards and industry guidelines that the manufacturer is embracing. ## Keywords\n\nComputer security; Cybersecurity Framework (CSF); distributed control systems (DCS); industrial control systems (ICS); information security; manufacturing; network security; programmable logic controllers (PLC); risk management; security controls; supervisory control and data acquisition (SCADA) systems. ## Supplemental Content\n\nAdditional volumes of this publication include:\n\nNISTIR 8183A Volume 2, Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide: Volume 2 - Process-based Manufacturing System Use Case. https://doi.org/10.6028/NIST.IR.8183A-2\n\nNISTIR 8183A Volume 3, Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide: Volume 3 - Discrete-based Manufacturing System Use Case."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does SHA-3 Derived Functions_ cSHAKE, KMAC, TupleHash, and ParallelHash provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-185\n\n## SHA-3 Derived Functions:\n\ncSHAKE, KMAC, TupleHash and ParallelHash\n\nJohn Kelsey Shu-jen Chang Ray Perlner\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-185\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-185\n\n## SHA-3 Derived Functions:\n\ncSHAKE, KMAC, TupleHash and ParallelHash\n\nJohn Kelsey Shu-jen Chang Ray Perlner Computer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-185\n\nDecember 2016\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. 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": "SHA-3 Derived Functions_ cSHAKE, KMAC, TupleHash, and ParallelHash", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 General Procedures for Registering Computer Security Objects provide? (Part 4)"}, {"role": "assistant", "content": "## Table of Contents | 1.0 | Introduction | Introduction | 1 | |-----------------------------------------------|-----------------------------------------------|-----------------------------------------------|-----| | | 1.1 | Purpose | 1 | | | 1.2 | Scope | 1 | | | 1.3 | Overview | 2 | | 2.0 | References | References | 2 | | 3.0 | Definitions and Abbreviations | Definitions and Abbreviations | 2 | | | 3.1 | Definitions | 2 | | | 3.2 | Abbreviations | 3 | | 4.0 | Registration Authority | Registration Authority | 4 | | 5.0 | Criteria for Eligibility | Criteria for Eligibility | 4 | | 6.0 | Processing of Applications | Processing of Applications | 4 | | | 6.1 Application for Registration | 6.1 Application for Registration | 4 | | | 6.2 | Review of Application | 5 | | | 6.3 | Assignment of CSO Names | 6 | | 7.0 | Maintenance of the Register | Maintenance of the Register | 7 | | 8.0 | Supplemental Services | Supplemental Services | 7 | | | 8.1 Register Inquiry | 8.1 Register Inquiry | 7 | | | 8.2 | Register Publication | 8 | | 9.0 | Fees |"}], "metadata": {"source": "General Procedures for Registering Computer Security Objects", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Computer Security Division 2013 Annual Report provide? (Part 5)"}, {"role": "assistant", "content": "|\n| Small and Medium Size Business (SMB) Outreach | ......................\n33 |\n| Cryptographic Technology ...................................................... | 33 |\n| Cryptographic Standards Program | ............................................ 33 |\n| Cryptographic Research .......................................................... | 36 |\n| New Research Areas in Cryptographic Techniques for Emerging Applications ............................................................. | 38 |\n| Applied Cryptography .............................................................. | 40 |\n| Identity Management | .............................................................. 42 |\n| Personal Identity Verification (PIV) and FIPS 201 Revision Efforts ...................................................................... | 42 |\n| PIV Program Test Cards ........................................................... | 43 |\n| NIST Personal Identity Verification Program (NPIVP) | ...................."}], "metadata": {"source": "Computer Security Division 2013 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Module-Lattice-Based Digital Signature Standard:\n\n| 1 Introduction | 1 Introduction | 1 Introduction | 1 Introduction | 1 |\n|-------------------------------------------|------------------------------------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------|-----|\n| | 1.1 | Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . | Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . | 1 |\n| | 1.2 | Context . . . . . . . . . . . . . . . . . . . . . . . . . | Context . . . . . . . . . . . . . . . . . . . . . . . . . | 1 |\n| 2 | 2 | Glossary | of Terms, Acronyms, and Symbols | 2 |\n| | 2.1 | Terms and Definitions . . . . . . . . . . . . . . | Terms and Definitions . . . . . . . . . . . . . . | 2 |\n| | 2.2 | Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 5 |\n| | 2.3 | Mathematical Symbols . . . . . . . . | . . . ."}], "metadata": {"source": "Module-Lattice-Based Digital Signature Standard", "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 Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n## 3.3. Optional Data Elements\n\n## 3.3.1. Printed Information\n\n## 3.3.2. Discovery Object"}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\n- Identify the business or operational environment and organization's purpose. - Identify all assets, including hardware, software, personnel, roles, responsibilities, and the assets' criticality. - Identify infrastructure that provides HSN functionality. - Identify the current and trending vulnerabilities, threats, and impacts should the threat be realized. The data, personnel, devices, systems, and facilities that enable the organization to achieve its business objectives are identified and managed in a manner that is consistent with their importance to organizational objectives and the organization's risk strategy. | Subcategory | Applicability to HSNs | Informative References |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|\n| ID.AM-5: Resources (e.g., hardware, devices, data, time, personnel, and software) are prioritized based on their classification, criticality, and business value."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "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 Secure Hash Standard (SHS) provide? (Part 5)"}, {"role": "assistant", "content": "o Obtain Copies of the Standard : This publication is available electronically by accessing http://csrc.nist.gov/publications/. Other computer security publications are available at the same web site.\n## Federal Information\n\n## Processing Standards Publication 180-4\n\n## Specifications for the\n\n## SECURE HASH STANDARD\n\n## Table of Contents\n\n| 1. | INTRODUCTION ...............................................................................................................................................3 | INTRODUCTION ...............................................................................................................................................3 | INTRODUCTION ...............................................................................................................................................3 |\n|------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2."}], "metadata": {"source": "Secure Hash Standard (SHS)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Guide to Storage Encryption Technologies for End User Devices:\n\n3.3.1 Use Case 1: Sharing a Laptop ... 3.3.1 Use Case 1: Sharing a Laptop\n\nThree users share a laptop."}], "metadata": {"source": "Guide to Storage Encryption Technologies for End User 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 System and Communications Protection?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog:\n\n| 1 Introduction ............................................................................................................8 | 1 Introduction ............................................................................................................8 |\n|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | Purpose and Applicability................................................................................ 8 |\n| 1.2 | Target Audience.............................................................................................. 9 |\n| | 1.3 Relationship to Other Publications.................................................................. 9 |\n| 1.4 | Publication Organization................................................................................."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "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 Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products provide? (Part 3)"}, {"role": "assistant", "content": "| 1.3 Document Scope and Goals...........................................................................\n| 2 |\n| | 1.4 Document Structure........................................................................................ | 2 |\n| 2 | Baseline Product Criteria ......................................................................................3 | Baseline Product Criteria ......................................................................................3 |\n| | 2.1 Scope of an IoT Product | ................................................................................. 3 |\n| | 2.2 Recommended Baseline Product | Criteria ......................................................."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Computer Security Division 2003 Annual Report provide?"}, {"role": "assistant", "content": "\n\n## TABLE OF CONTENTS\n\n| Welcome Letter | 2 |\n|-----------------------------------------------------|-----|\n| The Computer Security Division Responds to the | |\n| Federal Information Security Management Act of 2002 | 3 |\n| Outreach, Awareness and Education | 4 |\n| Security Management and Guidance | 8 |\n| Security Testing and Metrics | 14 |\n| Security Research and Emerging Technologies | 16 |\n| Cryptographic Standards and Applications | 26 |\n| Honors and Awards | 32 |\n| Computer Security Division Publications - 2003 | 34 |\n| Ways to Engage Our Division & NIST | 36 |\n\n\n\nF or many years, the Computer Security Division has made great contributions to help secure our nation's sensitive information and information systems. Our work has paralleled the evolution of IT , initially focused principally on mainframe computers, to now encompass today's wide gamut of information technology devices. Our important responsibilities were re-affirmed by Congress with passage of the Federal Information Security Management Act (FISMA) of 2002 and the Cyber Security Research and Development Act of 2002. Beyond our role to serve the Federal Agencies under FISMA, our standards and guidelines are often voluntarily used by U.S. industry, global industry, and foreign governments as sources of information and direction for securing information systems. Our research also contributes to securing the nation's critical infrastructure systems. Moreover, the Division has an active role in both national and international standards organizations in promoting the interests of security and U.S. industry."}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 2 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Computer Security Division 2010 Annual Report:\n\negisla­ tion in the federal government, including the Privacy Act of 1974, the Computer Security Act of 1987, the E-Government Act (includ­ ing FISMA), and other e-government services and initiatives.\nWe also invite public and private organizations to submit their in­ formation security practices to be considered for inclusion on the website. Policies and procedures may be submitted to us in any area of information security, such as accreditation, audit trails, au­ thorization of processing, budget planning and justification, cer­ tification, contingency planning, data integrity, disaster planning, documentation, hardware and system maintenance, identification and authentication, incident handling and response, life cycle, network security, personnel security, physical and environmental protection, production input/output controls, security policy, pro­ gram management, review of security controls, risk management, security awareness training and education (including specific training course and awareness materials), and security planning."}], "metadata": {"source": "Computer Security Division 2010 Annual Report", "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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Cell Phone Forensic Tools_ an Overview and Analysis:\n\n|\n| PDA SEIZURE ............................................................................................................................\n| 10 |\n| PILOT-LINK................................................................................................................................ CELL SEIZURE............................................................................................................................ | 11 11 |\n| GSM .XRY | ............................................................................................................................... 12 |\n| OXYGEN PHONE MANAGER | ....................................................................................................... 12 |\n| MOBILEDIT!............................................................................................................................."}], "metadata": {"source": "Cell Phone Forensic Tools_ an Overview and Analysis", "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 Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings:\n\nping for the secondary relationships. - Mapping can highlight ambiguities with wording, differences in granularity, duplication of concepts, and other issues within either of the sources being mapped.\nBe sure to capture and share these observations because they can significantly improve the next version of the affected sources."}], "metadata": {"source": "Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities:\n\nSecure Coding Principles | . . . . . . . . . . . . | 47 |\n| | 9.1. | Input/Output Check Safety . . . . . . . . . . . . . . . | 47 |\n| | 9.2. | Memory Safety . . . . . . . . . .\n| 48 |\n| | 9.3. | Data Type Safety . . . . . . . . . . . . . . . . . . | 50 |\n| 10. | BF Tools . . . . . . | . . . . . . . . . . . . . . . | 52 |\n| | 10.1. BFCWE Tool 10.2. | . . . . . . . . . . . . . . . . . . | 52 |\n| | BFCVE Tool | . . . . . . . . . . . . . . . . . . | 53 |"}], "metadata": {"source": "Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to PDA Forensic Tools_ an Overview and Analysis:\n\nThe purpose of this report is to inform law enforcement, incident response team members, and forensic examiners about the capabilities of present day forensic software tools that have the ability to acquire information from Personal Digital Assistant (PDAs) running the following Operating Systems: Palm OS, Pocket PC, and Linux. An overview of each tool describes the functional range and facilities for acquiring and analyzing evidence contained on PDAs. Generic scenarios were devised to mirror situations that often arise during a forensic examination of PDAs and associated media. The scenarios were used to reveal how selected tools react under various situations. Though generic scenarios were used in analyzing forensic tools, the procedures are not intended to serve as a formal product test or as a comprehensive evaluation. Additionally, no claims are made on the comparative benefits of one tool versus another. The report, instead, offers a broad and probing perspective on the state of the art of present-day forensic tools for PDA devices. It is important to distinguish this effort from the Computer Forensics Tool Testing (CFTT) project, whose objective is to provide measurable assurance to practitioners, researchers, and other users that the tools used in computer forensics investigations provide accurate results. Accomplishing this goal requires the development of rigorous specifications and test methods for computer forensics tools and the subsequent testing of specific tools against those specifications, which goes far beyond the analysis described in this document. The CFFT is the joint effort of the National Institute of Justice, the National Institute of Standards and Technology (NIST), the Office of Law Enforcement Standards (OLES), the U. S. Department of Defense, Federal Bureau of Investigation (FBI), U.S. Secret Service, the U.S. Immigration and Customs Enforcement (BICE), and other related agencies."}], "metadata": {"source": "PDA Forensic Tools_ an Overview and Analysis", "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 2019 NIST_ITL Cybersecurity Program Annual Report:\n\nd networking technologies. See https:/ /www.nist.gov/itl/how-work-us/itl-surf-program. - Opportunities for a temporary assignment of government or military personnel for 6- to 24-month details in ITL.\nQualified individuals should contact itl\\_inquiries@ nist.gov to provide qualifications and indicate the area of work that is of interest."}], "metadata": {"source": "2019 NIST_ITL Cybersecurity Program Annual Report", "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Directions in Security Metrics Research:\n\nSecurity Improve with Age?, 15th USENIX Security Symposium, Vancouver, B.C., Canada, July 31-August 4, 2006, http://www.usenix.org/events/sec06/tech/full\\_papers/ozment/ozment.pdf\n- [Pay06] Shirley C.\nPayne, A Guide to Security Metrics, SANS Security Essentials GSEC Practical Assignment, Version 1.2e, June 19, 2006, http://www.sans.org/reading\\_room/whitepapers/auditing/55.php\n- [Pou08] Kevin Poulsen, Researchers Use PlayStation Cluster to Forge a Web Skeleton Key, Wired Magazine, December 30, 2008, http://blog.wired.com/27bstroke6/2008/12/berlin.html\n- [Qua98] Richard E. Quandt, Measurement and Inference in Wine Tasting, Meetings of the Vineyard Data Quantification Society, Ajaccio, Corsica, October 2-3, 1998, http://www.liquidasset.com/corsica.htm\n- [Rei07a] Gavin Reid, Peter Mell, Karen Scarfone, CVSS-SIG Version 2 History, Forum of Incident Response and Security Teams, June 13, 2007, http://www.first.org/cvss/history.html\n- [Rei07b] Mark Reith, Jianwei Niu, William Winsborough, Apply Model Checking To Security Analysis in Trust Management, C107-0030, University of Texas at San Antonio, January 2, 2007, http://stinet.dtic.mil/cgibin/GetTRDoc?AD=ADA462754&Location=U2&doc=GetTRDoc.pdf\n- [Ron02] Juha Röning, Marko Laakso, Ari Takanen, Rauli Kaksonen, PROTOS Systematic Approach to Eliminate Software Vulnerabilities, Invited presentation at Microsoft Research, Seattle, Washington, May 6, 2002, http://www.ee.oulu.fi/research/ouspg/protos/sota/MSR2002-protos/index.html\n- [SAI07] Microsoft Windows Server 2003, XP Professional and XP Embedded Security Target, Version 3.0, Science Applications International Corporation, Common Criteria Testing Laboratory, November 19, 2007, http://www.commoncriteriaportal.org/files/epfiles/20080303\\_st\\_vid10184-st.pdf"}], "metadata": {"source": "Directions in Security Metrics Research", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Container Platform Security Prototype:\n\nAn attestation authority provides the definitive answers to these questions. Attestation provides cryptographic proof of compliance, utilizing the root of trust concept to provide actionable security controls by making the information from various roots of trust visible and usable by other entities. Figure 6 illustrates the attestation protocol providing the means for conveying measurements to the challenger. The endpoint attesting device must have a means of measuring the BIOS firmware, low-level device drivers, and OS and other measured components, and forwarding those measurements to the attestation authority. The attesting device must do this while protecting the integrity, authenticity, nonrepudiation, and in some cases, confidentiality of those measurements. 1. The challenger, at the request of a requester, creates a non-predictable nonce (NC) and sends it to the attestation agent on the attesting node, along with the selected list of Platform Configuration Registers (PCRs). 2. The attestation agent sends that request to the TPM as a TPMQuoteRequest with the nonce and the PCR List. 3. In response to the TPMQuote request, the TPM loads the attestation identity key from protected storage in the TPM by using the storage root key (SRK), and performs a TPM Quote command, which is used to sign the selected PCRs and the NC with the private key AIKpriv . Additionally, the attesting agent retrieves the stored measurement log (SML). 4. In the integrity response step, the attesting agent sends the response consisting of the signed quote, signed NC, and the SML to the challenger. The attesting agent also delivers the Attestation Identity Key (AIK) credential, which consists of the AIKpub that was signed by a privacy certificate authority (CA). 5. For the integrity verification step:\n- a. The challenger validates if the AIK credential was signed by a trusted Privacy-CA, thus belonging to a genuine TPM."}], "metadata": {"source": "Hardware-Enabled Security_ Container Platform Security Prototype", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management:\n\nHardware Asset Management (HWAM) Capability Definition, Overview, and Scope......2 | | 2.1 HWAM Capability Description...............................................................................................2 | | 2.2 HWAM Attack Scenarios and Desired Result.........................................................................2 | | 2.3 Assessment Objects Protected and Assessed by HWAM........................................................5 | | 2.4 Example HWAMData Requirements .....................................................................................6 | | 2.5 HWAM Concept of Operational Implementation ...................................................................8 | | 2.5.1 Collect Actual State...........................................................................................................9 | | 2.5.2 Collect Desired State ......................................................................................................10 | | 2.5.3 Find/Prioritize Defects....................................................................................................10 | | 2.6 SP 800-53 Control Items that Support HWAM.....................................................................10 | | 2.6.1 Process for Identifying Needed Controls........................................................................10 | | 2.6.2 Control Item Nomenclature ............................................................................................11 | | 2.7 HWAM Specific Roles and Responsibilities..........................................................................11 | | 2.8 HWAM Assessment Boundary ..............................................................................................13 | | 2.9 HWAM Actual State and Desired State Specification ..........................................................13 | | 2.10 HWAM Authorization Boundary and Inheritance ..............................................................14 | | 2.11 HWAM Assessment Criteria Recommended Scores and Risk-Acceptance Thresholds......14 | | 2.12 HWAM Assessment Criteria Device Groupings to Consider .............................................14 | | 3."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\n| Function | Category | Subcategory | Manufacturing Profile | Implementation Overview |\n|------------|------------------------------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Asset Management (ID.AM) | ID.AM-5 | Low Identify and prioritize manufacturing system components and functions based on their classification, criticality, and business value."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Best Practices for Privileged User PIV Authentication provide? (Part 3)"}, {"role": "assistant", "content": "|\n| 1.4 PIV-Based Authentication and Assurance Levels...........................................\n| 4 |\n| 2 Best Practices for PIV-Based Privileged | User Authentication...........................6 |\n| 2.1 Minimize Privileged Access ............................................................................ | 7 |\n| 2.2 Issue Dedicated Endpoint Devices for Privileged Use.................................... | 8 |\n| 2.3 Integrate LOA-3 and 4 Privileged Authentication Requirements into an Overall Risk-Based Approach ............................................................................................. | 9 |\n| 2.4 Select the Appropriate PIV Authentication Architecture................................ | 10 |\n| 2.5 Select and Implement Other Necessary Security Controls ..........................."}], "metadata": {"source": "Best Practices for Privileged User PIV Authentication", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n3.2.4 | Prevention Capabilities... 3.2.4 describe common security capabilities, divided into four categories: information gathering, logging, detection, and prevention, respectively. 3.2.4 Prevention Capabilities\n\nMost IDPSs offer multiple prevention capabilities; the specific capabilities vary by IDPS technology type."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "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 Guidelines for Securing Wireless Local Area Networks (WLANs):\n\n| Executive Summary.................................................................................................................vi | Executive Summary.................................................................................................................vi | Executive Summary.................................................................................................................vi |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. | Introduction ...................................................................................................................... 1 | Introduction ......................................................................................................................"}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "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 Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 4)"}, {"role": "assistant", "content": "0Cr1. ## Keywords\n\nCryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140; ISO/IEC 19790; ISO/IEC 24759; testing requirement; vendor evidence; vendor documentation; security policy.\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Supplemental Content\n\nSee https://csrc.nist.gov/projects/cmvp/sp800-140-series-info for details about the NIST Special Publication (SP) 800-140x series publications and their relationships to ISO/IEC 19790 and ISO/IEC 24759. ## Audience\n\nThis document is intended for use by vendors, testing labs, and the CMVP. ## Table of Contents\n\nScope ................................................................................................................................ 1\n\nNormative references ....................................................................................................... 1\n\nTerms and definitions ...................................................................................................... 1\n\nSymbols and abbreviated terms......................................................................................"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Managing Information Security Risk_ Organization, Mission, and Information System View:\n\nprocess level. An adverse event can have multiple consequences and different types of impact, at different levels, and in different time frames. For example, the exposure of sensitive information (e.g., personally identifiable information) by a particular mission/business area (e.g., human resources) can have organization-wide consequences and adverse impact with regard to reputation damage; the information system consequence/impact for multiple systems of an attacker more easily overcoming identification and authentication security controls; and the mission/business process consequence/impact (for one or more mission/business areas) of an attacker falsifying information on which future decisions are based. To ensure consistency, organizations determine at Tier 1, how consequences/impacts experienced in different time frames are to be assessed. At Tier 2, mission/business owners may amplify organizational guidance, as appropriate. The types of consequences and impact considered in risk determinations are identified to provide a basis for determining, aggregating, and/or consolidating risk results and to facilitate risk communication. Organizations also provide guidance to Tier 2 and Tier 3 with regard to the extent that risk assessments are to consider the risk to other organizations and the Nation. Organization make explicit any assumptions about the degree of impact/consequences related to specific threat sources (by name or by type) or through specific vulnerabilities (individually or by type). - Information System: Changes can occur in organizational information systems (including hardware, software, and firmware) that can introduce new risk or change existing risk. For example, updates to operating system software can eliminate security capabilities that existed in earlier versions, thus introducing new vulnerabilities into organizational information systems."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Study of Federal Agency Needs for Information Technology Security provide? (Part 5)"}, {"role": "assistant", "content": "lysis was based primarily on importance responses. ## FINDINGS AND OBSERVATIONS\n\n## General\n\nSome people are looking for the \"silver bullet\" for their security concerns, and, of course, there Is none.\nThe good news, however, is that there were very few of these people among those Interviewed and much of the help requested in the interviews and survey responses already exists or is being developed by NIST and others. Also, many agencies are making a significant effort to identify and solve\n\ntheir security probiems. Many security needs were expressed in the course of the study. Some were simpie. Some were complicated. Some were tangential. Many were fundamental. Most were Interrelated. The study team noted only 24 percent of the surveys expressed one or more additional needs and only 13 percent provided additional comments. A number of those interviewed expressed appreciation at the opportunity to focus on security, and also to discuss their problems and frustrations. A number of people said they saw the survey as a tool they could use to better understand the security needs of their constituency. Overall, needs related to technical approaches, methodologies, and products were rated higher in average importance than other subgroups of candidate needs. Needs in this group, in turn, consisted of a subgroup addressing \"specific security environments\" and a subgroup addressing \"particular areas of concern.\" The security environments subgroup included needs related to LANs, linking systems in one security architecture, integrating open system products, secure dial-in and laptops, and database security. This subgroup provided the strongest showing as a subgroup."}], "metadata": {"source": "A Study of Federal Agency Needs for Information Technology Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Applications Using Approved Hash Algorithms:\n\npopulation of possibilities and, in that sense, is unpredictable. A random number is an instance of an unbiased random variable, that is, the output produced by a uniformly distributed random process.\nRandom numbers may, e.g., be obtained by converting suitable stings of random bits (see [SP 800-90A], Appendix B.5 for details). |\n| Second preimage | A message X' , that is different from a given message X , such that its message digest is the same as the known message digest of X . |\n| Second preimage resistance | An expected property of a hash function whereby it is computationally infeasible to find a second preimage of a known message digest, See 'Second preimage'. |\n| Secret keying material | The binary data that is used to form secret keys, such as AES encryption orHMAC keys. |\n| Security strength (Also 'bits of security') | A number associated with the amount of work (that is, the number of operations) that is required to break a cryptographic algorithm or system. If 2 N execution operations of the algorithm (or system) are required to break the cryptographic algorithm, then the security strength is N bits. |\n| Shall | Used to indicate a requirement of this Recommendation. |\n| Shared secret | A secret value that has been computed using a key agreement algorithm and is used as input to a key derivation function. |"}], "metadata": {"source": "Recommendation for Applications Using Approved Hash Algorithms", "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 The NIST Cybersecurity Framework (CSF) 2.0:\n\n- improvement opportunities for the organization's policies, plans, processes, procedures, and practices that support cybersecurity risk management to inform efforts under all six Functions. - PROTECT (PR) -Safeguards to manage the organization's cybersecurity risks are used. Once assets and risks are identified and prioritized, PROTECT supports the ability to secure those assets to prevent or lower the likelihood and impact of adverse cybersecurity events, as well as to increase the likelihood and impact of taking advantage of opportunities. Outcomes covered by this Function include identity management, authentication, and access control; awareness and training; data security; platform security (i.e., securing the hardware, software, and services of physical and virtual platforms); and the resilience of technology infrastructure. - DETECT (DE) -Possible cybersecurity attacks and compromises are found and analyzed. DETECT enables the timely discovery and analysis of anomalies, indicators of compromise, and other potentially adverse events that may indicate that cybersecurity attacks and incidents are occurring. This Function supports successful incident response and recovery activities. - RESPOND (RS) -Actions regarding a detected cybersecurity incident are taken. RESPOND supports the ability to contain the effects of cybersecurity incidents. Outcomes within this Function cover incident management, analysis, mitigation, reporting, and communication. - RECOVER (RC) -Assets and operations affected by a cybersecurity incident are restored. RECOVER supports the timely restoration of normal operations to reduce the effects of cybersecurity incidents and enable appropriate communication during recovery efforts. ## 3.2."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "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 Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST.\n\n3.15. Exception and Error Handling . . . . . . . . . . . . . . . . . . . . . . .\n\n3.15.1. Requirements for Trusted Referees . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to General Server Security:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guide to General Server 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 is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Guidelines on Active Content and Mobile Code:\n\n3.1.2 Window of Exposure\n\nErrors of commission or omission invariably occur that create vulnerabilities that allow protection mechanisms to be bypassed or disabled. 3.1.2, February 4, 2002, http://www."}], "metadata": {"source": "Guidelines on Active Content and Mobile Code", "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 Personnel Security?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\na lower risk appetite may be less willing to accept risks left unmitigated by the lack of device cybersecurity requirements and thus not willing to omit the requirement if lacking from an IoT device.\nProper understanding of risk appetite and other cybersecurity considerations will require input from IT security personnel."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Guide for Security-Focused Configuration Management of Information Systems:\n\n3.2.2, fifth paragraph, fourth sentence: Changed 'OS' to 'operating system (OS)' | 33 |\n| 10/10/2019 | Editorial | Chapter Three, Section 3. 3.2.2. 3.2.2."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of 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 does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to Secure Web Services:\n\n| ........................................................................3-37 | | | 3.8.5 | Service Recursion | ......................................................................................3-38 | | | Securing the Discovery Service: Secure Interfaces to UDDI and WSDL...............3-38 | Securing the Discovery Service: Secure Interfaces to UDDI and WSDL...............3-38 | | | 3.9 | 3.9.1 | UDDI Structure | ...........................................................................................3-38 | | | 3.9.2 | UDDI Operations | ........................................................................................3-39 | | | 3.9.3 | Secure Access to the Registry | ...................................................................3-40 | | | 3.9.4 | Service Inquiry | API.....................................................................................3-40 | | | 3.9.5 | Service Publishing API | ...............................................................................3-41 | | | 3.9.6 | UDDI and WSDL | ........................................................................................3-42 | | | 3.10 Summary................................................................................................................3-42 | 3.10 Summary................................................................................................................3-42 | | | 4."}], "metadata": {"source": "Guide to Secure Web Services", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity of Genomic Data:\n\nThis report describes current practices in cybersecurity and privacy risk management for protecting genomic data, along with relevant challenges and concerns identified during 2022 NCCoE-hosted workshops with bioeconomy stakeholders and subsequent related research. Gaps that were identified by stakeholders include: practices across the lifecycle concerning genomic data generation; safe and responsible sharing of genomic data; monitoring the systems processing genomic data; lack of specific guidance documents addressing the unique needs of genomic data processors; and regulatory/policy gaps with respect to national security and privacy threats in the collection, storage, sharing, and aggregation of human genomic data. Cyber attacks targeted at genomic data include attacks against the confidentiality of the data, its integrity, and its availability. Cyber attacks against the confidentiality of the data can threaten our economy through theft of the intellectual property owned by the U.S. biotechnology industry, allowing competitors to gain an unfair economic advantage by accessing U.S. held genomic data. Attacks against the integrity of the data can disrupt biopharmaceutical output, agricultural food production, and bio-manufacturing activity. Attacks against the availability of the data include encrypting for ransom, deletion of data, and disabling critical automated equipment used in research, development, and manufacturing. The potential harms of cyber attacks on genomic data threaten our national security as well, including enabling development of biological weapons and\n\noppression, and extortion. Genomic database breaches or other losses of data may result in thefts of intellectual property and put the U.S. at a competitive disadvantage in biotechnology. As reported by national security experts, security threats may arise through the creation of bioweapons or compromised identities of national security agents [2][19]-[21]."}], "metadata": {"source": "Cybersecurity of Genomic Data", "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 Trustworthy Email provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-177\n\n## Revision 1\n\n## Trustworthy Email\n\nScott Rose J. Stephen Nightingale Simson Garfinkel Ramaswamy Chandramouli\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-177r1\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-177 Revision 1\n\n## Trustworthy Email\n\nScott Rose J. Stephen Nightingale * Advanced Network Technology Division Information Technology Laboratory\n\nSimson L. Garfinkel US Census Bureau\n\nRamaswamy Chandramouli Computer Security Division Information Technology Laboratory\n\n* Former employee; all work for this publication was done while at NIST\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-177r1\n\nFebruary 2019\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\n## Authority\n\n�is 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 f ederal officials exercising policy authority over such systems. �is guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A-130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Trustworthy Email", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 3)"}, {"role": "assistant", "content": "signed statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST publications, other than the ones noted above, are available at http://csrc.nist.gov/publications. ## Abstract\n\nProceedings of the Cybersecurity in Cyber-Physical Workshop, April 23 - 24, 2012, complete with abstracts and slides from presenters. Some of the cyber-physical systems covered during the first day of the workshop included networked automotive vehicles, networked medical devices, semi-conductor manufacturing, and cyber-physical testbeds. Day two of the workshop covered the electric smart grid. Dr. Farnham Jahanian, NSF, was the keynote speaker on day one. ## Keywords\n\nCPS; cyber-physical systems; cybersecurity; networked automotive vehicles; networked medical devices; semi-conductor manufacturing\n\n## Acknowledgements\n\nThe editor would like to thank Suzanne Lightman, Kevin Stine (both NIST), and Mark Enstrom (Neustar) for being reviewers for this document. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\nThis implies that threat analysis must consider both the type of threat and the various phases of the supply chain in which the threat is most effective. Moreover, one or more adversaries from different stages of supply chain can collaborate to compromise a hardware, which increases the severity of threats. Such insider threats are called collusion threats [6]. This work proposes a framework for analyzing different threats and how collusion among adversaries can affect the severity of threats. This analysis is divided into five distinct stages that discuss adversaries' intent, access, and resources, and how their collusion affects the severity of different threats. The framework is shown in Fig. 2. The framework incorporates threats across all stages of supply chain including insider threats. - [1] DARPA (2020) DARPA Selects Teams to Increase Security of Semiconductor Supply Chain. Available at https://www.darpa.mil/news/2020/semiconductor-supply-chainsecurity\n- [2] DARPA (2021) Expanding Domestic Manufacturing of Secure, Custom Chips for Defense Needs. Available at https://www.darpa.mil/news-events/2021-03-18\n- [3] NSWC Crane Corporate Communications (2019) NSWC Crane leverages OTA to ensure that the U.S. Government has access to secure state-of-the-art design, assembly, packaging and test for state-of-the-art microelectronics. Available at https://www.navsea.navy.mil/Media/News/Article/2005099/nswc-crane-leverages-otato-ensure-that-the-us-government-has-access-to-secure/\n- [4] Institute for Systems Research (2020) AFRL-Northrop Grumman: Locked Electronics for Assured Design (LEAD): Delay Locking ASIC IP Blocks to Protect Functionality. Available at https://isr.umd.edu/research-funding/afrl-northrop-grumman-locked-electronicsassured-design-lead-delay-locking-asic-ip\n- [5] Wolfe F (2020) Aether Spy Next-Generation Multi-Function Radar to Advance, Northrop Grumman Says. Defense Daily ."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Guidelines for Securing Wireless Local Area Networks (WLANs):\n\n3.1.2 Vulnerability Monitoring... 3.1.2 provide more information on these, respectively. 3.1.2 Vulnerability Monitoring\n\nOrganizations should do largely the same vulnerability monitoring for WLAN components that they do for any other software: identifying patches and applying them, and verifying security configuration settings and adjusting them as needed (see Section 2)."}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "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 Computer Security_ Selected Articles provide? (Part 3)"}, {"role": "assistant", "content": "echnical group that was sponsored by NIST from 1987 to 1990. The list provides titles, sources, and abstracts of important computer security publications that were relevant to the council's interests.\nThe National Institute of Standards and Technology (NIST) makes no claim or endorsement of the information provided. However, as this material may be of use to other organizations, NIST is reprinting the articles with permission as part of a continuing effort to assist federal agencies in accordance with NIST's mandate under the Computer Security Act of 1987. Questions regarding this publication should be addressed to National Institute of Standards and Technology, Computer Security Resource Center, A-216 Technology, Gaithersburg, MD 20899. Additional copies of this publication may be purchased through the National Technical Information Service, Springfield, VA 22161, telephone: (703) 487-4650. . Reprinting by permission of UNIXWORLD magazine. Copyright 1990, McGraw-Hill, Inc. ## IS YOUR SYSTEM SAFE? \n\nworm brought the Internet to its knees, the danger to UNIX networks still exists l · -arly this year, Cornell University graduate student i Robert T. Morris was convicted of creating a rogue fT' computer program - a 'worm' - and releasing it into the Internet. When this issue of UNIXWORLD went to press, Morris was still awaiting sentencing. But the evidence that convicted Morris brought home the stunning impact of the Internet's collapse. In all, the worm temporarily disabled as many as 3000 machines on the network, which links UNIX-based computers at universities, businesses, and military research facilities. By Frank Hayes\n\n\n\nIt took days of intensive work (8000 personnel hours, by one estimate) to isolate the worm and clear it from the Internet. No data was destroyed, but realistic estimates of time lost on the affected machines range as high as $10 million."}], "metadata": {"source": "Computer Security_ Selected Articles", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to Attribute Based Access Control (ABAC) Definition and Considerations provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-162\n\n## Guide to Attribute Based Access Control (ABAC) Definition and Considerations\n\nVincent C. Hu David Ferraiolo Rick Kuhn Adam Schnitzer Kenneth Sandlin Robert Miller Karen Scarfone\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-162\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-162\n\n## Guide to Attribute Based Access Control (ABAC) Definition and Considerations\n\nVincent C. Hu David Ferraiolo Rick Kuhn Computer Security Division Information Technology Laboratory\n\nAdam Schnitzer Booz Allen Hamilton\n\nKenneth Sandlin Robert Miller The MITRE Corporation\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-162\n\nJanuary 2014 INCLUDES UPDATES AS OF 08-02-2019; SEE PAGE IX\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Management Act (FISMA), Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources ."}], "metadata": {"source": "Guide to Attribute Based Access Control (ABAC) Definition and Considerations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes |\n|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| GV.SC-05 | Requirements to address cybersecurity risks in supply chains are established, prioritized, and integrated into contracts and other types of agreements with suppliers and other relevant third parties | Medium | R1: Cybersecurity supply chain risk management requirements should include cybersecurity performance and vulnerability, threat, and incident disclosure and information sharing."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\n3.2.3 Funds Control Information Type... 3.2.3 Funds Control Information Type\n\nFunds Control includes the management of the Federal budget process including the development of plans and programs, budgets, and performance outputs as well as financing Federal programs and operations through appropriation and apportionment of direct and reimbursable spending authority, fund transfers, investments and other financing mechanisms."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\n| ^^ SENSITIVITY/ ^S^RmCALlTY PROTECTION^. CATEGORY | LEVEL 2 (All level 0 and 1 considerations pius:) | LEVELS (All level 0, 1,and 2 considerations plus:) |\n|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ACCESS CONTROL | Protection measures that allow for: • Identification and authentication of individual users; • Restriction of functional capabilities of individual users; • Users to control access of other individual users to their data and applications; and . Data encryption. | Controls that can at all times restrict and log individual user access by system resource, application, and data files. Authorization to access system resources, appli^tions, and data files must be confirmed by the sponsors/owners (reconfirmation every 6 months). Non-use of encryption justified."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Reference Architecture:\n\nn cloud forensics include:\n- o The use of obfuscation, malware, data hiding, or other techniques to compromise the integrity of evidence\n- o Malware may circumvent virtual machine isolation methods\n5.\nIncident first responders (e.g., trustworthiness of cloud providers, response time, reconstruction). Incident first responder challenges in cloud forensics include:\n- o Confidence, competence, and trustworthiness of the cloud providers to act as first responders and perform data collection\n- o Difficulty in performing initial triage\n- o Processing a large volume of collected forensic artifacts\n6. Role management (e.g., data owners, identity management, users, access control). Role management challenges in cloud forensics include:\n- o Uniquely identifying the owner of an account\n- o Decoupling between cloud user credentials and physical users\n- o Ease of anonymity and creating fictitious identities online\n- o Determining exact ownership of data\n- o Authentication and access control\n7. Legal (e.g., jurisdictions, laws, service-level agreements, contracts, subpoenas, international cooperation, privacy, ethics). Legal challenges in cloud forensics include:\n- o Identifying and addressing issues of jurisdictions for legal access to data\n- o Lack of effective channels for international communication and cooperation during an investigation\n- o Data acquisition that relies on the cooperation, competence, and trustworthiness of cloud providers\n- o Missing terms in contracts and service-level agreements\n- o Issuing subpoenas without knowledge of the physical location of data\n8. Standards (e.g., standard operating procedures, interoperability, testing, validation). Standards challenges in cloud forensics include:\n- o Lack of minimum/basic SOPs, practices, and tools\n- o Lack of interoperability among cloud providers\n- o Lack of test and validation procedures\n9. Training (e.g., forensic investigators, cloud providers, qualification, certification)."}], "metadata": {"source": "NIST Cloud Computing Forensic Reference Architecture", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Key Performance Indicators for Process Control System Cybersecurity Performance Analysis:\n\nThis system employs a modular design which allows a greater flexibility for re-configuration and scalability. The major sub-systems and components are largely independent and have well-defined interfaces, leading to a greater flexibility to change the individual sub-systems, like the continuous manufacturing process simulation, the network topologies, or the industrial communication protocol. This allows the researcher to investigate a wide range of different settings of industrial manufacturing systems, and to study the impacts of the implementation of cybersecurity technologies on the system performance and operation.\n\nThe Process Control System is initialized in four stages: Stage one is the initialization of application software. In this stage, the OPC DA server, HMI, Data Historian, and the MATLAB Controller are executed and initialized. Stage two is the initialization of the hardware devices. In this stage, the configuration file of the multi-node DeviceNet card and the PLC are loaded and the devices enter run mode waiting for data input. Stage three is the industrial network activation stage. In this stage, the Plant Simulator is activated and all the sensor and actuator nodes are connected to the PLC. The last stage is the simulation start stage. In this stage, the Plant Simulator and Controller are started and all the sub-systems enter run mode.\n\nThe Key Performance Indicators (KPI) of the Process Control System are used to measure the performance of the system and its sub-systems. These KPIs are calculated in the baseline measurement, in which no additional cybersecurity measures are implemented, to form the basis of the performance of the system. In subsequent experiment runs, different cybersecurity measures are implemented and the KPIs are calculated again and compared to the baseline measurement. Analysis can be performed to understand the performance impact caused by the implementation of the cybersecurity measures."}], "metadata": {"source": "Key Performance Indicators for Process Control System Cybersecurity Performance Analysis", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1:\n\n| 3 | | | 1.1 | Authority....................................................................................................................3 | | | | 1.2 | Purpose and Scope...................................................................................................3 | | | | 1.3 | Audience ...................................................................................................................4 | | | | 1.4 | Document Structure | ..................................................................................................4 | | | 1.5 | Document Conventions | .............................................................................................4 | | 2."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n- [1] DARPA (2020) DARPA Selects Teams to Increase Security of Semiconductor Supply Chain. Available at https://www.darpa.mil/news/2020/semiconductor-supply-chainsecurity\n- [2] DARPA (2021) Expanding Domestic Manufacturing of Secure, Custom Chips for Defense Needs. Available at https://www.darpa.mil/news-events/2021-03-18\n- [3] NSWC Crane Corporate Communications (2019) NSWC Crane leverages OTA to ensure that the U.S. Government has access to secure state-of-the-art design, assembly, packaging and test for state-of-the-art microelectronics. Available at https://www.navsea.navy.mil/Media/News/Article/2005099/nswc-crane-leverages-otato-ensure-that-the-us-government-has-access-to-secure/\n- [4] Institute for Systems Research (2020) AFRL-Northrop Grumman: Locked Electronics for Assured Design (LEAD): Delay Locking ASIC IP Blocks to Protect Functionality. Available at https://isr.umd.edu/research-funding/afrl-northrop-grumman-locked-electronicsassured-design-lead-delay-locking-asic-ip\n- [5] Wolfe F (2020) Aether Spy Next-Generation Multi-Function Radar to Advance, Northrop Grumman Says. Defense Daily . Available at https://www.defensedaily.com/aether-spynext-generation-multi-function-radar-advance-northrop-grumman-says/air-force/\n- [6] CISA (2020) Defining Insider Threats. Available at https://www.cisa.gov/topics/physicalsecurity/insider-threat-mitigation/defining-insider-threats\n- [7] Areno M (2020) Supply chain threats against integrated circuits. Intel Whitepaper . Available at https://www.intel.com/content/dam/www/centrallibraries/us/en/documents/2022-08/supply-chain-threats-against-integrated-circuitswhitepaper-july2020.pdf\n- [8] Evernex (2024) EOL Meaning: What Does End of Life Mean for Your Hardware? Available at https://evernex.com/industry-guide/eol-meaning/\n- [9] Vincent J (2018) Chinese spies reportedly inserted microchips into servers used by Apple, Amazon, and others."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CA.L2-3.12.3 (NIST 3.12.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n3.12.3. 3.12.3). 3.12.3)."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "nist_control": "3.12.3", "cmmc_practice_id": "CA.L2-3.12.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 Guide to Computer Security Log Management:\n\n- GLYPH<c=31,font=/APONEK+Webdings> Antimalware Software. The most common form of antimalware software is antivirus software, which typically records all instances of detected malware, file and system disinfection attempts, and file quarantines. 3 Additionally, antivirus software might also record when malware scans were performed and when antivirus signature or software updates occurred. Antispyware software and other types of antimalware software (e.g., rootkit detectors) are also common sources of security information. - GLYPH<c=31,font=/APONEK+Webdings> Intrusion Detection and Intrusion Prevention Systems. Intrusion detection and intrusion prevention systems record detailed information on suspicious behavior and detected attacks, as well as any actions intrusion prevention systems performed to stop malicious activity in progress. Some intrusion detection systems, such as file integrity checking software, run periodically instead of continuously, so they generate log entries in batches instead of on an ongoing basis. 4\n- GLYPH<c=31,font=/APONEK+Webdings> Remote Access Software. Remote access is often granted and secured through virtual private networking (VPN). VPN systems typically log successful and failed login attempts, as well as the dates and times each user connected and disconnected, and the amount of data sent and received in each user session. VPN systems that support granular access control, such as many Secure Sockets Layer (SSL) VPNs, may log detailed information about the use of resources. - GLYPH<c=31,font=/APONEK+Webdings> Web Proxies. Web proxies are intermediate hosts through which Web sites are accessed. Web proxies make Web page requests on behalf of users, and they cache copies of retrieved Web pages to make additional accesses to those pages more efficient. Web proxies can also be used to restrict Web access and to add a layer of protection between Web clients and Web servers."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n3.1.1 | Typical Components... 3.1.1 Typical Components\n\nThe typical components in an IDPS solution are as follows:\n\n- GLYPH<c=31,font=/HHCKCL+Webdings> Sensor or Agent. 3.1.1 through 3."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance) provide? (Part 4)"}, {"role": "assistant", "content": "-85A, contains the test assertions and test procedures for testing smart card middleware as well as the card application. The tests reflect the design goals of interoperability and PIV Card functions.\n## Keywords\n\napplication programming interface (API); authentication; card command interface; derived test requirements (DTR); FIPS 201; identity credential; middleware; Personal Identity Verification (PIV); smart cards; test assertions\n\n## Acknowledgements\n\nThe authors (David Cooper, Hildegard Ferraiolo Ramaswamy Chandramouli of NIST, and Jason Mohler of Electrosoft Services, Inc.) wish to thank their colleagues who reviewed drafts of this document and contributed to its development. The authors also gratefully acknowledge and appreciate the many contributions from the public and private sectors whose thoughtful and constructive comments improved the quality and accuracy of this publication. ## ALIGNING REVISION NUMBERS\n\nWHAT HAPPENED TO SPECIAL PUBLICATION 800-85A REVISION 3 (SP 800-85A-3)? Revision numbers between NIST Special Publications 800-73 and 800-85A were misaligned from the start because the initial publication of SP 800-85A did not occur until after the publication of SP 800-73 Revision 1 (SP 800-73-1). This resulted in versions of the two documents corresponding as follows: SP 800-73-1 with SP 800-85A; SP 800-73-2 with SP 80085A-1 (i.e., Revision 1); and SP 800-73-3 with SP 800-85A-2. This revision numbering mismatch created ongoing uncertainty and confusion regarding which revision of SP 800-85A was consistent with which revision of SP 800-73. To reduce this uncertainty going forward, revision number 3 has been skipped for SP 800-85A, and the present version of SP 800-85A has been given revision number 4 (SP 800-85A-4) since this version is consistent with the updates to SP 800-73 Revision 4 (SP 800-73-4). Future revisions of SPs 80073 and 800-85A will maintain the revision number consistency. ## Table of Contents\n\n| 1."}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guidelines for Securing Wireless Local Area Networks (WLANs):\n\nOrganizations with WLANs should also have the capability to identify the physical location of a detected WLAN threat by using triangulation-estimating the threat's approximate distance from multiple sensors by the strength of the threat's signal received by each sensor, then calculating the physical location at which the threat would be the estimated distance from each sensor. This allows an organization to send appropriate personnel, such as physical security staff, to the location to address the threat."}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does ISCMA_ An Information Security Continuous Monitoring Program Assessment provide?"}, {"role": "assistant", "content": "## NISTIR 8212\n\n## ISCMA: An Information Security Continuous Monitoring Program Assessment\n\nKelley Dempsey Victoria Pillitteri Chad Baer Ron Rudman\n\nRobert Niemeyer\n\nSusan Urban\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8212\n\n\n\n## NISTIR 8212\n\n## ISCMA: An Information Security Continuous Monitoring Program Assessment\n\n## Kelley Dempsey Victoria Pillitteri\n\nComputer Security Division Information Technology Laboratory\n\n## Chad Baer\n\nCybersecurity and Infrastructure Security Agency U.S. Department of Homeland Security\n\nRon Rudman Robert Niemeyer Susan Urban The MITRE Corporation\n\nMcLean, VA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8212\n\nMarch 2021\n\n\n\nU.S. Department of Commerce\n\nGina Raimondo, Secretary\n\n## National Institute of Standards and Technology\n\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. 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": "ISCMA_ An Information Security Continuous Monitoring Program Assessment", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards:\n\nThe North American Electric Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) Reliability Standards [NERC CIP] are a set of requirements designed to mitigate the risk of a compromise that could lead to misoperation or instability in the Bulk Electric System (BES). The scope of the CIP Cyber Security Standards is restricted to BES Cyber Systems that would impact the reliable operation of the BES. The Reliability Standards cover topics like the identification and protection of BES Cyber Assets, defining logical isolation perimeters, personnel and training, BES Cyber System security management, disaster recovery planning, physical security, and supply chain risk management. | Function | Category Unique Identifier | Category |\n|------------|------------------------------|----------------------------------------|\n| Identify | ID. AM | Asset Management |\n| Identify | ID. BE | Business Environment |\n| Identify | ID."}], "metadata": {"source": "Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.2.2 rsakpg2-prime-factor ... 3.2.2 rsakpg2-prime-factor\n\nrsakpg2-prime-factor is the generator in the RSAKPG2 family such that the private key is in the prime-factor format ( p , q , d ). 3.2.2)."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\n| ORGANIZATIONAL RESPONSIBILITIES .........................................................................................\n| 2 |\n| 1.4 | RELATIONSHIPTOOTHERPUBLICATIONS ................................................................................... | 3 |\n| 1.5 | REVISIONSANDEXTENSIONS .................................................................................................... | 3 |\n| 1.6 | PUBLICATIONORGANIZATION .................................................................................................. | 3 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Computer Security Division 2005 Annual Report:\n\nonal-level personnel. We also invite public and private organizations to submit their information security practices to be considered for inclusion on the list of practices maintained on the Web site.\nPolicies and procedures may be submitted to us in any area of information security, including accreditation, audit trails, authorization of processing, budget planning and justification, certification, contingency planning, data integrity, disaster planning, documentation, hardware and system maintenance, identification and authentication, incident handling and response, life cycle, network security, personnel security, physical and environmental protection, production"}], "metadata": {"source": "Computer Security Division 2005 Annual Report", "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 Cryptographic Algorithms and Key Sizes for Personal Identity Verification provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-78-5\n\n## Cryptographic Algorithms and Key Sizes for Personal Identity Verification\n\nHildegard Ferraiolo Andrew Regenscheid\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-78-5\n\n\n\n## NIST Special Publication 800 NIST SP 800-78-5\n\n## Cryptographic Algorithms and Key Sizes for Personal Identity Verification\n\nHildegard Ferraiolo Andrew Regenscheid\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-78-5\n\nJuly 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST."}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Anonymous Consumer Goods Company:\n\nThe maturity of the Consumer Goods Company's cybersecurity and supply chain risk posture is driven by a combination of internal and external expertise. Third-party assessments are an important tool to capture relevant cyber risks and identify appropriate mitigations. The Consumer Goods Company engages cybersecurity and supply chain risk consultants to evaluate and stress test existing processes and controls. Each year, third-party assessments include compliance audits, penetration tests, strategic planning, and tabletop exercises. Tabletop exercises are dynamic simulations of a complex incident with representative stakeholders from every impacted domain, including CISO organization, commercial sourcing, legal, and executive leadership. These simulations have identified a number of opportunities to improve capabilities and processes, and the company intends to include representatives from critical suppliers in future exercises."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Anonymous Consumer Goods Company", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Liquefied Natural Gas:\n\n..............................................................................47 |\n| Appendix A.\n| List of Symbols, Abbreviations, and Acronyms............................................ | 49 |\n| Appendix B. | Glossary.............................................................................................................50 | |\n| Appendix C. | Change Log........................................................................................................"}], "metadata": {"source": "Cybersecurity Framework Profile for Liquefied Natural Gas", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.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 is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\n3.4.2 Inventory Control Information Type... 3.4.2 Inventory Control Information Type\n\nInventory control refers to the tracking of information related to procured assets and resources with regards to quantity, quality, and location."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "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 Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation provide? (Part 4)"}, {"role": "assistant", "content": "l comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nFIPS 201 defines the requirements and characteristics of government-wide interoperable identity credentials.\nIt specifies that these identity credentials must be stored on a smart card and that additional common identity credentials, known as derived PIV credentials, may be issued by a federal department or agency and used when a PIV Card is not practical. This document contains the technical specifications to interface with the smart card to retrieve and use PIV identity credentials. The specifications reflect the design goals of interoperability and PIV Card functions. The goals are addressed by specifying a PIV data model, card edge interface, and application programming interface. Moreover, this document enumerates requirements for the options and branches in international integrated circuit card standards. The specifications go further by constraining interpretations of the normative standards to ease implementation, facilitate interoperability, and ensure performance in a manner tailored for PIV applications. ## Keywords\n\nauthentication; FIPS 201; identity credential; logical access control; on-card biometric comparison; Personal Identity Verification (PIV); physical access control; smart cards; secure messaging. ## 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": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security Property Verification by Transition Model:\n\nThe author would like to express his thanks to Isabel Van Wyk and Jim Foti of NIST and Antonios Gouglidis of School of Computing and Communications Lancaster University for their detailed editorial review of both the public comment version and the final publication. Conference on Computer and Communications Security (CCS '11) (ACM, Chicago, IL) , pp . 163-174. https://dl.acm.org/doi/10.1145/2046707.2046727 [NU] Fondazione Bruno Kessler (2023) NuSMV: a new symbolic model checker. Available at https://nusmv.fbk.eu/ [NX] NetwokX developers (2024) NetworkX: Network Analysis in Python. Available at https://networkx.org/ [SF] NPTEL (2015) Safety properties described by automata. Available at https://www.youtube.com/watch?v=DzbqwlUw2-g [SP] Spin developers (2024) Verifying Multi-threaded Software with Spin. Available at https://spinroot.com/spin/whatispin.html [SP162] Hu VC, Ferraiolo DF, Kuhn DR, Schnitzer A, Sandlin K, Miller R, Scarfone KA (2014) Guide to Attribute Based Access Control (ABAC) Definition and Considerations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-162, Includes updates as of August 02, 2019. https://doi.org/10.6028/NIST.SP.800-162 [SP192] Hu VC, Kuhn DR, Yaga D (2017) Verification and Test Methods for Access Control Policies/Models. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-192. https://doi.org/10.6028/NIST.SP.800-192 [WP] Wikipedia (2024) Dining philosophers problem . Available at https://en.wikipedia.org/wiki/Dining\\_philosophers\\_problem [XA] OASIS Open (2023) XACML resources. Available at http://docs.oasis-open.org/xacml/ [YC] CTL* (2016) NPTEL National Program on Technology Enhanced learning . Available at https://www.youtube.com/watch?v=\\_2E5Q3CZ7g4&t=56s [YC2] CTL (2016) National Program on Technology Enhanced learning ."}], "metadata": {"source": "Security Property Verification by Transition Model", "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 Automation Support for Security Control Assessments_ Software Asset Management provide? (Part 3)"}, {"role": "assistant", "content": "security capability, adding tangible detail to the more general overview given in NISTIR 8011 Volume 1, and providing a template for transition to a detailed, NIST guidance-based automated assessment.\nThis document, Volume 3 of NISTIR 8011, addresses the Software Asset Management (SWAM) information security capability. The focus of the SWAM capability is to manage risk created by unmanaged or unauthorized software on a network. Unmanaged or unauthorized software is a target that attackers can use as a platform from which to attack components on the network. ## Keywords\n\nactual state; assessment; authorization boundary; automation; capability; continuous diagnostics and mitigation; dashboard; defect; desired state specification; firmware; information security continuous monitoring; ISCM; inventory management; malicious code; malware; mitigation; mobile code; ongoing assessment; root cause analysis; security capability; security control; security control item; software; software asset management; software file; SWID tag; whitelisting. ## Acknowledgments\n\nThe authors, Kelley Dempsey and Ned Goren of the National Institute of Standards and Technology (NIST), Paul Eavy of the Department of Homeland Security, and Dr. George Moore of the Applied Physics Laboratory at Johns Hopkins University, wish to thank their colleagues who reviewed drafts of this document and provided valuable input, including Nathan Aileo, Ujwala Arikatla, Mark Bunn, Jim Foti, John Groenveld, Susan Hansche, Blair Heiserman, Frank Husson, Mike Ko, Alan McClelland, Susan Pagan, David Waltermire, and Kimberly Watson . The authors also gratefully acknowledge and appreciate the comments and contributions made by government agencies, private organizations, and individuals in providing direction and assistance in the development of this document. ## Table of Contents\n\n| Executive Summary..................................................................................................................."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\nNISTIR 8183 Revision 1 updates the Manufacturing Profile to include the sub-category enhancements established in NIST Framework for Improving Critical Infrastructure Cybersecurity Version 1.1. These updates include managing cybersecurity within the supply chain, self-assessing cybersecurity risk, vulnerability disclosure, system integrity, and more comprehensive controls for identity management."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective provide? (Part 4)"}, {"role": "assistant", "content": "| Why is conformity assessment for cybersecurity standards important?\n....................................3 |\n| 3 | Core Areas in Cybersecurity Standardization ............................................................................4 |\n| 4 | Some Key IT Applications ..........................................................................................................6 |\n| 5 | Present State of International Cybersecurity Standardization ...................................................7 |\n| 6 | Standards Developing Organizations (SDOs) ..........................................................................."}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guide to IPsec VPNs:\n\nLooking at the SAD and SPD entries of the previous figures, it can be seen that the host with IP address 198.51.100.1 is allowed to send ESP packets to the host with IP 203.0.113.1. The encrypted IP packet included can only have the source IP address 192.168.13.6 but can have any destination IP address. AES-GCM is used as the AEAD encryption algorithm. In other words, there is a VPN client running on 198.51.100.1 that started a VPN connection to the VPN server on 203.0.113.1 and received the internal IP address 192.168.13.6.\n\nOther decisions should also be made during the design phase, such as setting IKE and IPsec SA lifetimes and identifying which DH group number is best. In addition to meeting the organization's cryptographic requirements of NIST SP 800-131A [18] and FIPS 140 [13][14], design decisions should incorporate the organization's logging and data management strategies, incident response and recovery plans, resource replication and failover needs, and current and future network characteristics, such as the use of wireless, NAT, and IPv6. Section 7.2.6 covers these considerations and design decisions in more detail.\n\nFor endpoints outside of the organization's control-such as systems belonging to business partners, users' home computers, and public internet access networks-organizations should recognize that some of the endpoints might violate the organization's minimum security standards. For example, some of these external endpoints might be compromised by malware and other threats; malicious activity could then enter the organization's networks from the endpoints through their IPsec connections. To minimize risk, organizations should restrict the access provided to external endpoints as much as possible and also ensure that policies, processes, and technologies are in place to detect and respond to suspicious activity. Organizations should be prepared to identify users or endpoint devices of interest and disable their IPsec access rapidly as needed."}], "metadata": {"source": "Guide to IPsec VPNs", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\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 is CMMC practice AT.L2-3.2.7 (NIST 3.2.7)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.2.7) • Added ECDH key agreement scheme (SP 800-73-5 Part 2, Sec."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "nist_control": "3.2.7", "cmmc_practice_id": "AT.L2-3.2.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n| Scope.........................................................................................................................\n| 3 |\n| | Audience | .................................................................................................................... 3 |\n| | Document Structure.................................................................................................... | 3 |\n| | Document Conventions | .............................................................................................. 4 |\n| Overview of Mobile Devices ............................................................................................ | Overview of Mobile Devices ............................................................................................"}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "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 Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis provide? (Part 3)"}, {"role": "assistant", "content": "ii | | 1 | Introduction.......................................................................................................................................1 | | 2 | Robotic Enclave .................................................................................................................................1 | | 2.1 | Server Operations .......................................................................................................................2 | | 2.2 | Emulated Manufacturing Operation...........................................................................................3 | | 2.3 | Network Architecture .................................................................................................................3 | | 2.4 | Process Operations and Data Flow.............................................................................................5 | | 3 | Metrics and KPI..................................................................................................................................6 | | 3.1 | Terminology ................................................................................................................................7 | | 3.2 | Selection Process ........................................................................................................................7 | | 4 | Measurement Methodologies...........................................................................................................7 | | 4.1 | Manufacturing process Performance .........................................................................................8 | | 4.2 | Robot Performance.....................................................................................................................9 | | 4.3 | Network Performance...............................................................................................................10 | | 4.4 | Programmable Logic Controller Performance..........................................................................11 | | 4.5 | Server Performance ..................................................................................................................11 | | 5 | Appendix A - Description of Measurements and KPI......................................................................13 | | 6 | Appendix B - References.................................................................................................................39 | | LIST OF FIGURES | |-------------------------------------------------------------------------------------------------------------------------------------------------| | Figure 1 - View of the robotic enclave and its components...................................................................2 | | Figure 2 - Flow chart of the emulated manufacturing process..............................................................3 | | Figure 3 - Diagram of the network architecture and its components....................................................4 | | Figure 4 - Data flow diagram..................................................................................................................5 | | LIST OF TABLES | |-----------------------------------------------------------------------------------------------------------------------------------------------| | Table 1 - Manufacturing Process Metrics...............................................................................................8 | | Table 2 - Manufacturing Process KPI......................................................................................................8 | |"}], "metadata": {"source": "Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Security Segmentation in a Small Manufacturing Environment support CMMC certification?"}, {"role": "assistant", "content": "According to Security Segmentation in a Small Manufacturing Environment:\n\nve (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nManufacturers are increasingly targeted in cyber-attacks.\nSmall manufacturers are particularly vulnerable due to limitations in staff and resources to operate facilities and manage cybersecurity. Security segmentation is a cost-effective and efficient security design approach for protecting cyber assets by grouping them based on both their communication and security requirements. This paper outlines a six-step approach that manufacturers can follow to implement security segmentation and mitigate cyber vulnerabilities in their manufacturing environments. The security architecture resulting from the security segmentation design activities is a foundational preparation step for additional security strategies like Zero Trust. ## Keywords\n\nAssets; cyber risk mitigation; industrial control systems; manufacturing; security architecture; security controls; security requirements; security segmentation; security strategy. ## Audience\n\nThe intended audience is managers of information technology and operational technology (IT/OT) systems at small manufacturing organizations. This may include roles of company owner, operations manager, and, if technical resources are present, network and security architect or even the Chief Information Officer/Chief Information Security Officer (CIO/CISO). This paper is intended for those who are interested in implementing a cost-effective and efficient mitigation for cyber vulnerabilities in small manufacturing environments."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to Operational Technology (OT) Security:\n\nThis document is the third revision of NIST SP 800-82. Updates in this revision include:\n\n• Updates to OT threats and vulnerabilities\n\n• Updates to OT risk management, recommended practices, and architectures"}], "metadata": {"source": "Guide to Operational Technology (OT) Security", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3:\n\n3.5.1] with the following changes:\n\n1."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to 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 Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines on Firewalls and Firewall Policy:\n\nThe authors also wish to express their thanks to the individuals and organizations that contributed to the original version of the publication, including John Wack of NIST and Ken Cutler and Jamie Pole of the MIS Training Institute, who authored the original version, and other contributors and reviewersparticularly Peter Batista and Wayne Bavry (U.S. Treasury); Harriet Feldman (Integrated Computer Engineering, Inc.); Rex Sanders (U.S. Geological Survey); and Timothy Grance, D. Richard Kuhn, Peter Mell, Gale Richter, and Murugiah Souppaya (NIST). Stateful inspection improves on the functions of packet filters by tracking the state of connections and blocking packets that deviate from the expected state. This is accomplished by incorporating greater awareness of the transport layer. As with packet filtering, stateful inspection intercepts packets at the network layer and inspects them to see if they are permitted by an existing firewall rule, but unlike packet filtering, stateful inspection keeps track of each connection in a state table. While the details of state table entries vary by firewall product, they typically include source IP address, destination IP address, port numbers, and connection state information. Firewalls with application-proxy gateways can also have several disadvantages when compared to packet filtering and stateful inspection. First, because of the 'full packet awareness' of application-proxy gateways, the firewall spends much more time reading and interpreting each packet. Because of this, some of these gateways are poorly suited to high-bandwidth or real-time applications-but applicationproxy gateways rated for high bandwidth are available. To reduce the load on the firewall, a dedicated proxy server (discussed in Section 2.1.5) can be used to secure less time-sensitive services such as email and most web traffic."}], "metadata": {"source": "Guidelines on Firewalls and Firewall Policy", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## 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-05-06\n\n## How to Cite this NIST Technical Series Publication\n\nMegas, K, Fagan M, Cuthill B, Hoehn B , Petrella E (2025) Workshop Summary Report for 'Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' . (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8572. https://doi.org/10.6028/NIST.IR.8572\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448\n\nMichael Fagan: 0000-0002-1861-2609\n\nBarbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8572/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis report summarizes discussions held at the March 5, 2025 \"Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' organized by the NIST Cybersecurity for the Internet of Things (IoT) program."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to 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 Module-Lattice-Based Digital Signature Standard provide? (Part 2)"}, {"role": "assistant", "content": "gainst adversaries in possession of a large-scale quantum computer. Keywords: cryptography; digital signatures; Federal Information Processing Standards; lattice; postquantum; public-key cryptography.\n## Federal Information Processing Standards Publication 204\n\nPublished:\n\nAugust 13, 2024\n\nEffective:\n\nAugust 13, 2024\n\n## Announcing the Module-Lattice-Based\n\n## Digital Signature Standard\n\nFederal Information Processing Standards (FIPS) publications are developed by the National Institute of Standards and Technology (NIST) under 15 U.S.C. 278g-3 and issued by the Secretary of Commerce under 40 U.S.C. 11331. 1. Name of Standard. Module-Lattice-Based Digital Signature Standard (FIPS 204). 2. Category of Standard. Computer Security. Subcategory. Cryptography. 3. Explanation. This standard specifies ML-DSA, a lattice-based digital signature algorithm for applications that require a digital signature rather than a written signature. Additional digital signature schemes are specified and approved in other NIST Special Publications and FIPS publications (e.g., FIPS 186-5 [1]). A digital signature is represented in a computer as a string of bits and computed using a set of rules and parameters that allow the identity of the signatory and the integrity of the data to be verified. Digital signatures may be generated on both stored and transmitted data. Signature generation uses a private key to generate a digital signature. Signature verification uses a public key that corresponds to but is not the same as the private key. Each signatory possesses a key-pair composed of a private key and a corresponding public key. Public keys may be known by the public, but private keys must be kept secret. Anyone can verify the signature by employing the signatory's public key. Only the user who possesses the private key can generate a signature that can be verified by the corresponding public key. The digital signature is provided to the intended verifier along with the signed data."}], "metadata": {"source": "Module-Lattice-Based Digital Signature Standard", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nSupport for Streamlined SCAP Content Creation, Acquisition, and Reuse: SCAP v2 will develop and incorporate simpler formats for use in content creation, including updates to the Extensible Configuration Checklist Description Format (XCCDF) and the\n\nOpen Vulnerability and Assessment Language (OVAL), and will develop ways to use system artifacts in posture assessments that do not require deep system expertise. Additionally, by using standardized interfaces and protocols to discover and retrieve SCAP content, SCAP v2 products will be able to detect when new SCAP content is available and automatically acquire suitable content updates based on organizational policies. These same interfaces can be used to discover content for reuse. - Posture Evaluator Protocol : To support the separation of collection and evaluation, SCAP v2 will need to define a remote evaluation protocol to enable Posture Evaluators to be plugged into the architecture. This protocol will need to define how to request an evaluation and how a Posture Evaluator can request Endpoint posture to be collected from a Posture Collection Server. - XCCDF Language Improvements: XCCDF currently uses the CPE Applicability language. XCCDF [18] needs to be updated to support the Endpoint Applicability Language and SWID tags. There are also several extensibility enhancements requested by the SCAP community that need to be addressed. These updates are expected to be worked in an international standards organization. - OVAL-Based Collection and Language Improvements: A messaging model is needed to allow for the collection of configuration setting information from an endpoint using OVAL [19]. A NEA extension will be developed to allow for event-driven and ad-hoc OVAL-based collection of configuration setting information."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Reference Architecture:\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 costeffective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. This publication was developed by the NIST Cloud Computing Forensic Science Working Group (NCC FSWG) co-chaired by Dr. Martin Herman and Dr. Michaela Iorga. NIST and the co-chairs wish to gratefully acknowledge and thank the members whose dedicated efforts contributed significantly to researching this topic and to generating the data included in this publication, which constitutes the foundation of NIST's Cloud Computing Forensic Reference Architecture."}], "metadata": {"source": "NIST Cloud Computing Forensic Reference Architecture", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters provide? (Part 5)"}, {"role": "assistant", "content": "s may be out of scope for CAVP or CMVP validation testing and are thus the responsibility of entities using, implementing, installing, or configuring applications that incorporate this Recommendation.\nConformant implementations may perform procedures via an equivalent sequence of operations, provided that these include all cryptographic checks included with the specifications in this document. This is important because the checks are essential for the prevention of subtle attacks. ## 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": "Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines on Active Content and Mobile Code:\n\nResponding to computer security incidents effectively necessitates a significant amount of preparation. Incident response activities require technical knowledge as well as effective communication and coordination among personnel who respond to the incident, to return the system as quickly as possible to normal operations. Proper periodic backup of critical files is a key ingredient in recovering from the adverse effects of an incident. NIST SP 800-61, Computer Security Incident Handling Guide [NIST04] provides an overview of the processes necessary for organizations to develop effective incident handling programs and policies."}], "metadata": {"source": "Guidelines on Active Content and Mobile Code", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Threat Assessment of Malicious Code and External Attacks:\n\nToday, desktop workstations are becoming the tool of more and more scientists and professionals. Without proper time and training to administer these systems, vulnerability to both internal and external attacks will increase. Workstations are usually administered by individuals whose primary job description is not the administration of the workstation. The workstation is merely a tool to assist in the performance of the actual job tasks. As a result, if the workstation is up and running, the individual is satisfied.\n\nOf course, even with proper training and adequate tools threats will remain. New security bugs and attack mechanisms will be employed. Proper channels do not currently exist in most organizations for the dissemination of security related information. If organizations do not place a high enough priority on computer security, the average system will continue to be at risk from external threats.\n\nPoor administrative practices and the lack of education, tools, and controls combine to leave the average system vulnerable to attack. Research promises to alleviate the inadequate supply of tools and applicable controls. These controls, however, tend to be add-on controls. There is a need for the delivery of secure systems, rather than the ability to build one from parts. The average administrator has little inclination to perform these modifications, and no idea how to perform them."}], "metadata": {"source": "Threat Assessment of Malicious Code and External Attacks", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nMalware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures. It also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones. Malware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. Organizations also face similar threats from a few forms of non-malware threats that are often associated with malware. One of these forms that has become commonplace is phishing, which is using deceptive computer-based means to trick individuals into disclosing sensitive information. Organizations should perform threat mitigation to detect and stop malware before it can affect its targets. The most commonly used malware threat mitigation technical control is antivirus software; organizations should deploy antivirus software on all hosts for which satisfactory antivirus software is available."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products:\n\nmer -grade router' is a router intended for residential use and can be installed by the customer. Routers forward data packets, most commonly Internet Protocol (IP) packets, between networked systems.\nT hroughout this document, the term 'router' is used as a shorthand for 'consumer -grade router.' As technology advances, the need for robust router cybersecurity becomes ever more critical to maintain a safe and trustworthy digital environment."}], "metadata": {"source": "Recommended Cybersecurity Requirements for Consumer-Grade Router Products", "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 Mobile Forensic Reference Materials_ a Methodology and Reification provide? (Part 3)"}, {"role": "assistant", "content": "----------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| 2.\n| Background ...........................................................................................................................2 | Background ...........................................................................................................................2 |\n| 3. | Forensic Reference Material .................................................................................................3 | Forensic Reference Material .................................................................................................3 |\n| 4. | Identity Modules ....................................................................................................................4 | Identity Modules ....................................................................................................................4 |\n| 4.1 File System Organization | 4.1 File System Organization | ...............................................................................................4 |\n| 4.2 Data Coverage | 4.2 Data Coverage | ...............................................................................................................5 |\n| 5."}], "metadata": {"source": "Mobile Forensic Reference Materials_ a Methodology and Reification", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 PBX Administrator’s Security Standards provide? (Part 5)"}, {"role": "assistant", "content": "Use Networking Services Effectively | 3-17 | | Physically Protect All Equipment | 3-17 | | Security of Diskettes, Tapes, Backups and other Computer Related Equipment | 3-18 | | Ensure Physical Security of Shared Equipment | 3-19 | | Secure Building Cable Plant Access Points | 3-19 | | Apply PBX Security Measures to Key Telephone Systems | 3-20 | | Maintain Up-to-Date Records of Configuration | 3-20 | | Maintain Copies of Contractual Agreements | 3-21 | | Make End Users Aware of Their Responsibilities | 3-22 | | Summary of End User Responsibilities | 3-23 | | Report All Security Incidents | 3-24 | | Section 4: Future Concerns | | | Looking Toward the Future | 4-1 | | Common Channel Signaling System 7 (CCSS7) | 4-1 | | Appendix | | | Appendix: Terms and Definitions | A-1 | ## Section 1: FDIC Telephone Policy •?.-."}], "metadata": {"source": "PBX Administrator’s Security Standards", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Security Property Verification by Transition Model:\n\n3.1.4. 3.1.4."}], "metadata": {"source": "Security Property Verification by Transition Model", "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 does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management:\n\nThe authors wish to thank all individuals, organizations, and enterprises that contributed to the creation of this document. This includes Lisa Carnahan, Amy Mahn, Chris Enloe, Santi Kiran, Matt Scholl, and Kevin Stine of NIST; Matthew Smith and Daniel Topper of Huntington Ingalls Industries; Mat Heyman of Impresa Management Solutions. Organizations and individuals who provided feedback on the public comment drafts include: David Austin of Bible.org; Julie Chua, Linda Esah, Elizabeth Flaim, Kim Isaac, Nnake Nweke, Brent Roddy, Nicole Rohloff, and Musarat Qadri Shaikh of the Cyber-ERM Community of Interest; Melanie Tiano of CTIA; Frederick Doyle of CubicPrism Analytics, Inc.; Alicia Jones of Entergy Services, Inc.; Luke Bader of FAIR Institute; Bernice Harvey of Harvey Consulting & Training LLC; Janet Anderson of the National Security Agency, Kelly Hood and Tom Conkle of Optic Cyber Solutions; Amy Hamilton of the U.S. Department of Energy; the Executive Secretariat of the U.S. Department of Energy; and the U.S. Department of Health and Human Services Team; individual contributors include Louise Dandonneau and Carmen Estigarribia. - NISTIR 8286A (this report) provides additional detail regarding risk context, scenario identification, and analysis of likelihood and impact. It also includes methods to convey risk information, such as through cybersecurity risk registers (CSRRs) and risk detail records (RDRs). Similar processes, and the general use of risk registers, are helpful to identify and manage other types of risk, including those for Cyber Supply Chain and Privacy. - NISTIR 8286B describes ways to apply risk analysis to prioritize cybersecurity risk, evaluate and select appropriate risk response, and communicate risk activities as part of an enterprise CSRM strategy. - NISTIR 8286C describes processes for aggregating information from CSRM activities throughout the enterprise."}], "metadata": {"source": "Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Implementation of DevSecOps for a Microservices-based Application with Service Mesh provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-204C\n\n## Implementation of DevSecOps for a Microservices-based Application with Service Mesh\n\nRamaswamy Chandramouli\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-204C\n\n\n\n## NIST Special Publication 800-204C\n\n## Implementation of DevSecOps for a Microservices-based Application with Service Mesh\n\nRamaswamy Chandramouli\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-204C\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## 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": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guidelines for Securing Radio Frequency Identification (RFID) Systems:\n\n| versus RFID Systems ....................3-10 |\n| Table 4-1.\nFactors Influencing Business Process | Risk.............................................................4-2 |\n| Table 4-2. Factors Influencing Business Intelligence | Risk........................................................4-4 |\n| Table 4-3. Factors Influencing Cyber Attack | Risk.....................................................................4-8 |\n| Table 5-1. RFID Controls | Summary........................................................................................5-26 |\n| Table 6-1. OECD Basic Principles: Guidelines on the Protection of Privacy and Transborder Flows of Personal Data......................................................................................................6-4 | |\n| Table 6-2."}], "metadata": {"source": "Guidelines for Securing Radio Frequency Identification (RFID) 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 Physical Protection?"}, {"role": "assistant", "content": "According to Metrics and Methodology for Hardware Security Constructs:\n\ngineering, and physical security. CAPEC also analyzes the likelihood of such attacks being launched, their potential severity and flow of execution, and the skills that an adversary is likely to need.\n| ID | Description |\n|----------|-----------------------------------------------------------------------|\n| CWE-1272 | Sensitive Information Uncleared Before Debug/Power State Transition |\n| CWE-1300 | Improper Protection of Physical Side Channels |\n| CWE-1189 | Improper Isolation of Shared Resources on System-on-a-Chip (SoC) |\n| CWE-1244 | Internal Asset Exposed to Unsafe Debug Access Level or State |\n| CWE-1191 | On-Chip Debug and Test Interface with Improper Access Control |\n| CWE-1231 | Improper Prevention of Lock Bit Modification |\n| CWE-1233 | Security-Sensitive Hardware Controls with Missing Lock Bit Protection |\n| CWE-1274 | Improper Access Control for Volatile Memory Containing Boot Code |\n| CWE-1260 | Improper Handling of Overlap Between Protected Memory Ranges |\n| CWE-1240 | Use of a Cryptographic Primitive with a Risky Implementation |\n| CWE-1256 | Improper Restriction of Software Interfaces to Hardware Features |"}], "metadata": {"source": "Metrics and Methodology for Hardware Security Constructs", "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 Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach provide? (Part 5)"}, {"role": "assistant", "content": "he trustworthiness of systems with the capability to anticipate, withstand, recover from, and\nadapt to adverse conditions, stresses, attacks, or compromises that use or are enabled by cyber\nresources.\nFrom a risk management perspective, cyber resiliency is intended to help reduce the\nmission, business, organizational, enterprise, or sector risk of depending on cyber resources. This publication can be used in conjunction with ISO/IEC/IEEE 15288:2015, Systems and\nsoftware engineering—Systems life cycle processes; NIST Special Publication (SP) 800-160,\nVolume 1, Systems Security Engineering—Considerations for a Multidisciplinary Approach in the\nEngineering of Trustworthy Secure Systems; NIST SP 800-37, Risk Management Framework for\nInformation Systems and Organizations—A System Life Cycle Approach for Security and Privacy;\nand NIST SP 800-53, Security and Privacy Controls for Information Systems and Organizations. It\ncan be viewed as a handbook for achieving the identified cyber resiliency outcomes based on a\nsystems engineering perspective on system life cycle and risk management processes, allowing\nthe experience and expertise of the implementing organization to help determine how the\ncontent will be used for its purpose. Organizations can select, adapt, and use some or all of the\ncyber resiliency constructs (i.e., goals, objectives, techniques, approaches, and design principles)\ndescribed in this publication and apply the constructs to the technical, operational, and threat\nenvironments for which systems need to be engineered. KEYWORDS\n\nAdvanced persistent threat; controls; cyber resiliency; cyber resiliency approaches; cyber\nresiliency design principles; cyber resiliency engineering framework; cyber resiliency goals; cyber\nresiliency objectives; cyber resiliency techniques; risk management strategy; system life cycle;\nsystems security engineering; trustworthiness."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight:\n\n|\n| Appendix A. Change Log...................................................................................................................39 |\n| List of Tables Table 1.\nExamples of Cybersecurity Risk Normalization .......................................................................8 |\n\nNotably, while the quote above is based on a U.S. Government directive, similar considerations for aggregate risk evaluation apply to private sector organizations. These include requirements from the U.S. Securities and Exchange Commission (SEC) 10 and core principles from the international Basel Committee on Banking Supervision. 11 Since exposure can affect investments, partner cooperation, credit lines, and other financial aspects, evaluation is critical for all types of enterprises."}], "metadata": {"source": "Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Integrating Cybersecurity and Enterprise Risk Management (ERM):\n\no fully address targeted attacks, they represent a way to quickly identify some common vulnerabilities. However, cybersecurity weaknesses are not limited to the hardware and software of an enterprise.\nReviewing the NIST SP 800-53 controls immediately highlights the breadth of potential threats germane to cybersecurity, such as those that result from a lack of risk planning associated with Continuity of Operations (COOP), training, monitoring physical access, power considerations, and supply chain considerations."}], "metadata": {"source": "Integrating Cybersecurity and Enterprise Risk Management (ERM)", "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 Recommended Criteria for Cybersecurity Labeling of Consumer Software:\n\nThis document is not intended to describe how a cybersecurity label should be explicitly represented (either physically or digitally) - nor is it intended to detail how a labeling program should be owned or operated.\n\nSoftware is constantly being updated and modified. Likewise, a label may need to be amended, updated, or revoked. Elapsed time between the publishing of a label (especially regarding labels printed on physical packaging) and receipt by the consumer may cause confusion concerning the status of the label's claims.\n\n- Is available for consumers to view before and at the time and place of software selection as well as at a later time, as needed.\n- Supports physical or digital formats as appropriate depending on the manner in which the software can be selected.\n- The date (year at a minimum) when the label was asserted should be included on the label.\n- The claimant is using a label that has undergone rigorous consumer testing to ensure its usability."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling of Consumer Software", "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 Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1:\n\nanization's own cybersecurity requirements. However, the variety of ways in which the Framework can be used by an organization means that phrases like 'compliance with the Framework' can be confusing.\n|\n| A new section on self- assessment | Added Section 4.0 Self-Assessing Cybersecurity Risk with the Framework to explain how the Framework can be used by organizations to understand and assess their cybersecurity risk, including the use of measurements. |\n| Greatly expanded explanation of using Framework for Cyber Supply Chain Risk Management purposes | An expanded Section 3.3 Communicating Cybersecurity Requirements with Stakeholders helps users better understand Cyber Supply Chain Risk Management (SCRM), while a new Section 3.4 Buying Decisions highlights use of the Framework in understanding risk associated with commercial off-the-shelf products and services. Additional Cyber SCRM criteria were added to the Implementation Tiers. Finally, a Supply Chain Risk Management Category, including multiple Subcategories, has been added to the Framework Core. |\n| Refinements to better account for authentication, authorization, and identity proofing | The language of the Access Control Category has been refined to better account for authentication, authorization, and identity proofing. This included adding one Subcategory each for Authentication and Identity Proofing. Also, the Category has been renamed to Identity Management and Access Control (PR.AC) to better represent the scope of the Category and corresponding Subcategories. |\n| Better explanation of the relationship between Implementation Tiers and Profiles | Added language to Section 3.2 Establishing or Improving a Cybersecurity Program on using Framework Tiers in Framework implementation."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Verification and Test Methods for Access Control Policies_Models:\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\nTo address the issue, the AC Rule Logic Circuit Simulation (ACRLCS) technique [HS13], which enables the AC authors to detect a fault when the fault-causing AC rule is added to the model, so the fixing can be implemented in real time (on the spot) before adding other rules that further complicate the detecting effort. In other words, instead of checking by retracing the interrelations between rules after the policy is completed, the policy author needs only check the new added rule against previous 'correct' ones. In ACRLCS, AC rules are represented in a simulated logic circuit (SLC) (pronounced CELL-see). By simulation, it means ACRLCS is not necessarily implementable by a physical electronic circuit; however, the concept can be implemented and computed through simulated software.\n\nProcedures and controls that limit or detect access to critical information resources. This can be accomplished through software, biometrics devices, or physical access to a controlled space."}], "metadata": {"source": "Verification and Test Methods for Access Control Policies_Models", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to SRI International_ Improving the Security of Your UNIX System:\n\n3.4.3 | The Is Command | 34 |\n| 3. 3.4.3 The Is Command\n\nSimple as its function is."}], "metadata": {"source": "SRI International_ Improving the Security of Your UNIX System", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n1. Concept: Concept stage is the birthplace of an Integrated Circuit (IC). At this stage, the goals and purpose of an integrated circuit (IC) are formulated, and the scope and target of a hardware component are discussed. Customers, the design, planning, finance teams, and other key stakeholders are involved at this stage. 2. Design: Design stage gives a form to the ideas generated in the concept stage. This is the stage where prototypes of the concept are created with the help of different Computer Aided Design (CAD) tools and analysis of whether the goals identified during the concept stage are met. This stage also includes the use of third-party software and hardware prototyping. 3. Integration: Integration is the stage where different design components from designers and third parties are integrated together. This phase is crucial since many design elements already have tested solutions, so not everything needs to be created from the ground up. It is more feasible to purchase these solutions from third parties and integrate them into the design. 4. Manufacturing: After the IC's design is finished, the manufacturing phase begins. This stage includes several processes, including fabrication and packaging. Due to the high cost of building and maintaining manufacturing facilities, many design houses are fabless and outsource their designs to manufacturers located elsewhere. 5. Testing: Testing is the stage at which manufactured Integrated Circuits (ICs) are tested to ensure that they perform properly. Following the completion of fabrication, each IC undergoes testing. An IC's functionalities are tested here to make sure they adhere to design specifications. 6. Provisioning: Provisioning is the stage where standard and sensitive data are loaded into the manufactured IC. Standard data are generic and mostly available open source, but the sensitive data are anything whose disclosure would compromise IP or security."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Analysis of First Responder Mobile and Wearable Devices:\n\ngement, 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| 1 | Introduction ............................................................................................................1 | Introduction ............................................................................................................1 |\n|-----|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| | 1.1 Purpose | .......................................................................................................... 1 |\n| | 1.2 Scope.............................................................................................................. | 2 |\n| | 1.3 Previous Work | ................................................................................................ 2 |\n| | 1.4 Document Structure........................................................................................ | 2 |\n| | 1.5 Document Conventions..................................................................................."}], "metadata": {"source": "Security Analysis of First Responder Mobile and Wearable Devices", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories:\n\nll NIST documents mentioned in this publication, other than the ones noted above, are available at http://csrc.nist.gov/publications. The authors, Kevin Stine, Rich Kissel, and William C.\nBarker, wish to thank their colleagues, Jim Fahlsing and Jessica Gulick from Science Applications International Corporation (SAIC), who helped update this document, prepare drafts, and review materials. In addition, special thanks are due to our reviewers, Arnold Johnson (NIST), Karen Quigg (Mitre Corporation), and Ruth Bandler (Food and Drug Administration), who greatly contributed to the document's development. A special note of thanks goes to Elizabeth Lennon for her superb technical editing and administrative support. NIST also gratefully acknowledges and appreciates the many contributions from individuals in the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\nBecause each organization has unique security needs, security products have been applied on a case by case basis to meet individual security threats and concerns. Products should be flexible enough to serve a broad spectrum of security needs at the operating system level, the application level, the organizational level, and the site level. Organizational security requirements also change over time and cannot be totally specified at the time of product acquisition. This study has attempted to identify basic security needs of information technology product users, administrators, developers, and evaluators based on actual organizational practices."}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Managing Information Security Risk_ Organization, Mission, and Information System View:\n\n- '... Through the process of risk management, leaders must consider risk to U.S. interests from adversaries using cyberspace to their advantage and from our own efforts to employ the global nature of cyberspace to achieve objectives in military, intelligence, and business operations... '\n- ' ... For operational plans development, the combination of threats, vulnerabilities, and impacts must be evaluated in order to identify important trends and decide where effort should be applied to eliminate or reduce threat capabilities; eliminate or reduce vulnerabilities; and assess, coordinate, and deconflict all cyberspace operations... '\n- ' ... Leaders at all levels are accountable for ensuring readiness and security to the same degree as in any other domain... '\n- -- THE NATIONAL STRATEGY FOR CYBERSPACE OPERATIONS OFFICE OF THE CHAIRMAN, JOINT CHIEFS OF STAFF, U.S. DEPARTMENT OF DEFENSE\n\nI nformation technology is widely recognized as the engine that drives the U.S. economy, giving industry a competitive advantage in global markets, enabling the federal government to provide better services to its citizens, and facilitating greater productivity as a nation. Organizations 5 in the public and private sectors depend on technology-intensive information systems 6 to successfully carry out their missions and business functions. Information systems can include diverse entities ranging from high-end supercomputers, workstations, personal computers, cellular telephones, and personal digital assistants to very specialized systems (e.g., weapons systems, telecommunications systems, industrial/process control systems, and environmental control systems)."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Usability and Security Considerations for Public Safety Mobile Authentication:\n\nIn the United States over 10 000 jurisdictions employ public safety personnel to respond to emergency situations every day. These first responders treat life-threatening injuries, deal with the consequences of natural disasters, fight crime, and combat terrorism. To perform these duties, emergency responders must undergo unique training, utilize specialized equipment, and access a variety of information systems. The use of specialized tools, information systems, and protective equipment places first responders within a unique environment to perform their jobs.\n\nA variety of roles exist for LEOs, for example patrol officers, riot police, motorcycle patrol, detectives, highway patrol, sheriffs, and mounted policemen. Many of these roles exist at varying levels of government (i.e., federal, state, local, tribal). LEOs face threats from potentially malicious intelligent adversaries on a daily basis. LEOs receive specialized training and must operate in hostile environments requiring quick decision-making under high stress.\n\nPasswords used for local authentication to a mobile device's lockscreen tend to be generated/managed by a user, and are shorter than passwords generated for remote authentication scenarios, since passwords for local authentication do not have to be resistant to the same set of threats. While there are many ways to measure the security of user generated passwords (e.g., [11], [17], [18]), the field of computer security lacks a universally agreed upon measurement standard with sufficient evidence to prove the merit of the standard. This method of authentication is vulnerable to shoulder surfing attacks."}], "metadata": {"source": "Usability and Security Considerations for Public Safety Mobile Authentication", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators:\n\n3.1.4, a step was inserted that will provide backtracking resistance (step 14 of the pseudocode)."}], "metadata": {"source": "Recommendation for Random Number Generation Using Deterministic Random Bit Generators", "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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\n| Scope..............................................................................................................\n| 2 |\n| | 1.2.1 Alternative Configurations | ....................................................................3 |\n| 1.3 | Document Conventions................................................................................... | 3 |\n| 2 TLS Overview .........................................................................................................4 | 2 TLS Overview .........................................................................................................4 | 2 TLS Overview .........................................................................................................4 |\n| 2.1 | TLS Subprotocols | ..........................................................................................."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\nreas span those that are common to the entire IT infrastructure, such as physical security, authentication and authorization, change management, configuration control, incident response, and recovery.\nWithin these areas, security controls that are specific to storage technologies, such as network-attached storage (NAS) and storage area networks (SAN), are also covered. In addition, security recommendations specific to storage technologies are provided for the following areas of operation in the storage infrastructure:"}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\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\n4. Testing . Monitoring or auditing mode, available in most whitelisting technologies, allows software managers to estimate the impact on resources before enforcing whitelisting. Monitoring allows planning for resource requirements in advance of actual implementation.\n5. Attributes . Increasingly, organizations are implementing whitelisting products that support more granular whitelisting attributes, such as Software Identification (SWID) tags. 11 In the Guide to Application Whitelisting (2015), the authors note:\n\nTable 8: Low Baseline Control (Item) Allocation Table, Table 9: Moderate Baseline Control (Item) Allocation Table, and Table 10: High Baseline Control (Item) Allocation Table, provide the low, moderate, and high baseline control allocations, respectively. The following is a summary of the material in the security plan assessment narrative for each determination statement in Section 3.3. It provides a concise summary of the assessment plan."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program:\n\n3.1.2. 3.1.2."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "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 Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products:\n\n6. Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations , SP 800-161 Rev. 1 [SP800-161r1]\n7. Secure Software Development Framework (SSDF) Version 1.1: Recommendations for Mitigating the Risk of Software Vulnerabilities , SP 800-218 [SSDF]\n8. Information technology -Security techniques -Vulnerability disclosure processes , ISO/IEC 29147 [ISO29147]\n9. Information technology -Security techniques -Vulnerability handling , ISO/IEC 30111 [ISO30111]\n10. Risk management -Guidelines , ISO 31000 [ISO31000]\n11. Systems and software engineering -Design and development of information for users , ISO/IEC/IEEE 26514 [ISO26514]\n\n[WHAnnouncement] White House (2023) BidenHarris Administration Announces Cybersecurity Labeling Program for Smart Devices to Protect American Consumers. (White House, Washington, DC). https://www.whitehouse.gov/briefing-room/statementsreleases/2023/07/18/biden-harris-administration-announces-cybersecurity-labelingprogram-for-smart-devices-to-protect-american-consumers/ [IR8425] Fagan M, Megas KN, Watrobski P, Marron J, Cuthill B (2022) Profile of the IoT Core Baseline for Consumer IoT Products. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8425. https://doi.org/10.6028/NIST.IR.8425 [BBF] Walls, J, Editor (2022) Functional Requirements for Broadband Residential Gateway Devices. (Broadband Forum, Fremont, CA), Technical Report (TR) 124, Issue 8. https://www.broadband-forum.org/pdfs/tr-124-8-0-0.pdf [CableLabs] CableLabs Security (2021) Gateway Device Security Best Common Practices. (CableLabs, Louisville, CO), CL-GL-GDS-BCP-V01-211007. https://community.cablelabs.com/wiki/plugins/servlet/cablelabs/alfresco/download?id=1 209eea3-bd81-40cb-9a18-21bd6cfcd80d [BSI] Federal Office for Information Security (2023) Secure Broadband Router: Requirements for Secure Broadband Routers."}], "metadata": {"source": "Recommended Cybersecurity Requirements for Consumer-Grade Router Products", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide for Cybersecurity Event Recovery:\n\nIntroduction .........................................................................................................................1 | | | | 1.1 | Background.................................................................................................................1 | | | | 1.2 | Purpose and Scope | ....................................................................................................2 | | | 1.3 | Audience.....................................................................................................................2 | | | | 1.4 | Document Structure....................................................................................................3 | | | 2."}], "metadata": {"source": "Guide for Cybersecurity Event Recovery", "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 Security Considerations for Voice Over IP Systems provide? (Part 4)"}, {"role": "assistant", "content": "| |----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 Introduction ......................................................................................................................................10 | 1 Introduction ......................................................................................................................................10 | 1 Introduction ......................................................................................................................................10 | | 1.1 | Authority | ....................................................................................................................................10 | | 1.2 | Document Scope and Purpose ..................................................................................................10 | | | 1.3 | Audience and Assumptions.......................................................................................................11 | | | 1.4 | Document Organization ............................................................................................................11 | | | 2 Overview of VOIP............................................................................................................................13 | 2 Overview of VOIP............................................................................................................................13 | 2 Overview of VOIP............................................................................................................................13 | | .......................................................................................................................13 | .......................................................................................................................13 | .......................................................................................................................13 | | 2.1 | VOIP Equipment | | | 2.2 | Overview of VOIP Data Handling ...........................................................................................14 | | | 2.3 | Cost.............................................................................................................................................16 | | | 2.4 | Speed and Quality......................................................................................................................16 | | | 2.5 | Privacy and Legal Issues with VOIP........................................................................................17 | | | 2.6 | VOIP Security Issues.................................................................................................................17 | | | 3 Quality of Service Issues..................................................................................................................19 | 3 Quality of Service Issues..................................................................................................................19 | 3 Quality of Service Issues..................................................................................................................19 | | 3.1 | Latency.......................................................................................................................................19 | | | 3.2 | Jitter ............................................................................................................................................20 | | | 3.3 | Packet Loss | ................................................................................................................................21 | | 3.4 | Bandwidth &Effective Bandwidth ..........................................................................................22 | | | 3.5 | The Need for Speed...................................................................................................................24 | | | 3.6 | Power Failure and Backup Systems .........................................................................................24 | | | 3.7 | Quality of Service Implications for Security............................................................................25"}], "metadata": {"source": "Security Considerations for Voice Over IP Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guide to Computer Security Log Management:\n\nrusion prevention systems record detailed information on suspicious behavior and detected attacks, as well as any actions intrusion prevention systems performed to stop malicious activity in progress.\nSome intrusion detection systems, such as file integrity checking software, run periodically instead of continuously, so they generate log entries in batches instead of on an ongoing basis. 4\n- GLYPH<c=31,font=/APONEK+Webdings> Remote Access Software. Remote access is often granted and secured through virtual private networking (VPN). VPN systems typically log successful and failed login attempts, as well as the dates and times each user connected and disconnected, and the amount of data sent and received in each user session. VPN systems that support granular access control, such as many Secure Sockets Layer (SSL) VPNs, may log detailed information about the use of resources. - GLYPH<c=31,font=/APONEK+Webdings> Web Proxies. Web proxies are intermediate hosts through which Web sites are accessed. Web proxies make Web page requests on behalf of users, and they cache copies of retrieved Web pages to make additional accesses to those pages more efficient. Web proxies can also be used to restrict Web access and to add a layer of protection between Web clients and Web servers. Web proxies often keep a record of all URLs accessed through them. - GLYPH<c=31,font=/APONEK+Webdings> Vulnerability Management Software. Vulnerability management software, which includes patch management software and vulnerability assessment software, typically logs the patch installation history and vulnerability status of each host, which includes known vulnerabilities and missing software updates. 5 Vulnerability management software may also record additional information about hosts' configurations. Vulnerability management software typically runs occasionally, not continuously, and is likely to generate large batches of log entries."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Directions in Security Metrics Research:\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 Interagency Report discusses ITL's research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations.\n\nMore than 100 years ago, Lord Kelvin insightfully observed that measurement is vital to deep knowledge and understanding in physical science. During the last few decades, researchers have made various attempts to develop measures and systems of measurement for computer security with varying degrees of success. This paper provides an overview of the security metrics area and looks at possible avenues of research that could be pursued to advance the state of the art.\n\n'At a high-level, metrics are quantifiable measurements of some aspect of a system or enterprise. For an entity (system, product, or other) for which security is a meaningful concept, there are some identifiable attributes that collectively characterize the security of that entity. Further, a security metric (or combination of security metrics) is a quantitative measure of how much of that attribute the entity possesses. A security metric can be built from lower-level physical measures.' [ISS08]"}], "metadata": {"source": "Directions in Security Metrics Research", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide for Conducting Risk Assessments:\n\nrganizations 5 in the public and private sectors depend on information technology 6 and information systems 7 to successfully carry out their missions and business functions. Information systems can include very diverse entities ranging from office networks, financial and personnel systems to very specialized systems (e.g., industrial/process control systems, weapons systems, telecommunications systems, and environmental control systems). Information systems are subject to serious threats that can have adverse effects on organizational operations and assets, individuals, other organizations, and the Nation by exploiting both known and unknown vulnerabilities to compromise the confidentiality, integrity, or availability of the information being processed, stored, or transmitted by those systems. Threats to information systems can include purposeful attacks, environmental disruptions, human/machine errors, and structural failures, and can result in harm to the national and economic security interests of the United States. Therefore, it is imperative that leaders and managers at all levels understand their responsibilities and are held accountable for managing information security risk-that is, the risk associated with the operation and use of information systems that support the missions and business functions of their organizations. O\n\nRisk assessment is a key component of a holistic, organization-wide risk management process as defined in NIST Special Publication 800-39, Managing Information Security Risk: Organization, Mission, and Information System View . Risk management processes include: (i) framing risk; (ii) assessing risk; (iii) responding to risk; and (iv) monitoring risk. Figure 1 illustrates the four steps in the risk management process-including the risk assessment step and the information and communications flows necessary to make the process work effectively."}], "metadata": {"source": "Guide for Conducting Risk Assessments", "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 Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium:\n\n-  Mandatory scanning (enumeration) of system prior to deploying to the network and disable all unneeded communications/system processes,\n-  Review of user accounts/groups on the system including their level of privilege and adjust accordingly,\n-  Removal of all unneeded applications installed on the system (browsers, readers, games, etc.),\n-  Enable host based firewall to allow communication via secure ports to know IP addresses for manufacturer communications (disable this connectivity when not in use)\n-  Processes developed for system updates/upgrades\n\n-  Altering data to change specs of finish products\n-  Availability\n-  Components in sensitive applications may have unintended / undesirable performance characteristics that are undetectable\n-  Confidentiality\n-  Corruption of imbedded software @ machine\n-  Corruption of STL files\n-  Damage of manufacturing equipment\n-  Design tools vulnerability -> CAD & pre-cad part of\n-  Detection of inherent flaw - pilphereal IP is analyzed for existing flaw\n-  Ensure the small & medium enterprise have the tools are reasonable price point\n-  EtherCat or Industrial IP security? -  Getting tools to the right level capability at right price / affordable\n-  Government entities each seem to have their own program for cyber security. The risk is two-fold: (1) they are talking, but not WORKING together. Wasting resources and efforts (2) Government is way behind industry, and not bringing them in to address this substantial gap\n-  Integrity\n-  IT/OT convergence --> how do I secure this… …\n-  IVV of file transport from central storage to production facility\n-  Modification of model\n-  OEMs not ensuring security (& keeping backdoors open for \"maintenance\")\n-  Tainted products (additional functionality)\n-  The human aspect (social engineering)\n-  Theft of intell property\n-  Theft of IP\n-  Treats to RF specturm - wireless is increasing the comms component of choice on factory floor."}], "metadata": {"source": "Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| | security requirements and risks during software design (secure by design) is key for improving software security and also helps improve development efficiency."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\n3.3.3 Low Baseline Security Control Item Narratives ... 3.3.3). 3.3.3 ) | (2) Moderate Control Items ( Section 3."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "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 Configuration Management?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nives), there need to be different tiers of metrics based on the audience or user. For example, the CWE structure could be used to define security requirements that lead to associated security metrics.\nJason noted that CWEs for hardware are relatively new, starting around 2020, compared to CWEs' long track record for software, which started around 2006. Since CWEs point out common root cause weaknesses that lead to vulnerabilities, they foster a more proactive approach by allowing security issues to be discovered and mitigated earlier in the hardware development life cycle, thus lowering the financial impact. Having good metrics that can be used to inform design and business decisions would be helpful to the semiconductor community. Finally, Mark Tehranipoor from the University of Florida emphasized the importance of thinking about security and associated metrics in the early stages of the hardware development life cycle. Specifically, this involves conducting a security and risk assessment and developing a"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Existing Application-Specific Key Derivation Functions:\n\nConformance testing for implementations of this Recommendation will be conducted within the framework of the Cryptographic Module Validation Program (CMVP) and the Cryptographic Algorithm Validation Program (CAVP). The requirements of this Recommendation are indicated by the word ' shall .' Some of these requirements may be out-of-scope for CMVP or CAVP validation testing, and thus are the responsibility of entities using, implementing, installing or configuring applications that incorporate this Recommendation."}], "metadata": {"source": "Recommendation for Existing Application-Specific Key Derivation Functions", "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 Proxy Validation and Verification for Critical AI Systems_ A Proxy Design Process:\n\nSystem characteristics can be analyzed by reviewing its domain and goals, such as determining whether a system domain is in the area of communication, learning, planning, reasoning, or providing a service. Overall AI goals can then be identified, such as language processing, computer vision, deep learning, data science, or machine learning. This analysis informs the next phase of determining operational characteristics. For example, if a goal of a CAIS is to operate autonomously, the proxy must also be the same type of autonomous system.\n\n| | Phy. Op. Envmt. | AI App. Purpose | Operational Charac. | Dev. Algorithm | Dev. Tech. |\n|--------------------|-------------------|-----------------------------------------|--------------------------------------|------------------|--------------|\n| Autonomous Vehicle | Land | Reasoning, learning, planning, services | O1:1; 02: 11111; O3: 0; O4: 9; 05: 9 | KMP Algorithm | Java |\n\n| | Phy. Op. Envmt. | AI App. Purpose | Operational Charac. | Dev. Algorithm | Dev. Tech. |\n|------------------|-------------------|-----------------------------------------|--------------------------------------|------------------|--------------|\n| RobotWeed Killer | Land | Reasoning, learning, planning, services | O1:1; 02: 11111; O3: 0; O4: 0; 05: 9 | KMP Algorithm | Java |\n| RobotVacuum | Land | Reasoning, learning, planning, services | O1:1; 02: 11111; O3: 0; O4: 0; 05: 9 | KMP Algorithm | Java |"}], "metadata": {"source": "Proxy Validation and Verification for Critical AI Systems_ A Proxy Design 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 Personnel Security?"}, {"role": "assistant", "content": "According to Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results:\n\nToday, Blue Cross of California interacts with the United States government in health care as a Medicare processor. We have also bid on the contract to become the CHAMPUS processor in California and Hawaii. (As you may know, CHAMPUS is the program to provide medical coverage to dependents of military personnel.) These interactions are different from traditional claims processing that starts with the provider and ends with the payer. With Medicare and CHAMPUS, the electronic path of a claim continues on to the HCFA or DoD agency. I thought it would be interesting to look at some of the information requirements of those two agencies as an example ofthe public-private data exchange partnership now in place.\n\naccess control: this attribute is designed to prevent the use of the system by unauthorized personnel or in an unauthorized manner. A company would not want its telecommunication system to be tapped into and used to order and reroute merchandise or other assets to some enterprising hacker.\n\nAccess control; This attribute is designed to prevent the use of the system by unauthorized personnel or in an unauthorized manner."}], "metadata": {"source": "Workshop on Security Procedures for the Interchange of Electronic Documents_ Selected Papers and Results", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Application Whitelisting:\n\nAn application whitelist is a list of applications and application components that are authorized for use in an organization. Application whitelisting technologies use whitelists to control which applications are permitted to execute on a host. This helps to stop the execution of malware, unlicensed software, and other unauthorized software. This publication is intended to assist organizations in understanding the basics of application whitelisting. It also explains planning and implementation for whitelisting technologies throughout the security deployment lifecycle. An application whitelist is a list of applications and application components (libraries, configuration files, etc.) that are authorized to be present or active on a host according to a well-defined baseline. The technologies used to apply application whitelists-to control which applications are permitted to install or execute on a host-are called whitelisting programs , application control programs, or application whitelisting technologies . Application whitelisting technologies are intended to stop the execution of malware and other unauthorized software. Unlike security technologies such as antivirus software, which block known bad activity and permit all other, application whitelisting technologies are designed to permit known good activity and block all other. The purpose of this publication is to assist organizations in understanding the basics of application whitelisting and planning for its implementation. An application whitelist is a list of applications and application components (libraries, configuration files, etc.) that are authorized to be present or active on a host according to a well-defined baseline. The technologies used to enforce application whitelists-to control which applications are permitted to be installed or executed on a host-are called whitelisting programs , application control programs, or application whitelisting technologies ."}], "metadata": {"source": "Guide to Application Whitelisting", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework 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": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\n| | Introduction .........................................................................................................................1 | Introduction .........................................................................................................................1 | |---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| | | Purpose.........................................................................................................................2 | | | | Scope............................................................................................................................2 | | | | Audience | .......................................................................................................................4 | | Intended Use........................................................................................................................5 | Intended Use........................................................................................................................5 | | | | EV/XFC Cybersecurity Mission Objectives.......................................................................5 | EV/XFC Cybersecurity Mission Objectives.......................................................................5 | | | Mission Objective 1: Deliver Reliable Performance through Secure Communications.6 | | | | Mission Objective 2: Maintain Resilience of the XFC Infrastructure..............................7 | | | | Mission Objective 3: Build and Maintain Trustworthy Relationships with Partners and Customers..............................................................................................................7 | | | | Mission Objective 4: Maintain Continuity of Operations................................................8 | | | | Overview of the Cybersecurity Framework ......................................................................8 | | | | The Framework Core ....................................................................................................9 | | | | Sector-Level Profiles | ...................................................................................................12 | | | XFC Baseline Profile .........................................................................................................12 | | | | Identify Function..........................................................................................................12 | | | 5.1.1."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "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 Recommendation for Block Cipher Modes of Operation_ Three Variants of Ciphertext Stealing for CBC Mode:\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 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."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Three Variants of Ciphertext Stealing for CBC Mode", "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 Quick Start Guide for Populating Mobile Test Devices:\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": "Quick Start Guide for Populating Mobile Test Devices", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cloud Computing Synopsis and Recommendations:\n\nprobably need to be taken offline for maintenance at various times and therefore two-way communication in advance among the community members is essential to achieving a clear understanding of the service levels that they offer to one another and require from one another. Generally, for outsourced or public SaaS clouds, consumers need not become involved with the management of a provider's infrastructure. For example, consumers need not be distracted by which operating system, hardware devices or configuration choices, or software library versions underlie a SaaS application. In particular, providers have responsibility for operational issues such as backups, system maintenance, security patches, power management, hardware refresh, physical plant security, etc. Providers also have an obligation to field services that guard against known exploits at the application level. Further, consumers are not required to maintain on premises IT support to perform these tasks, with\n\nAs illustrated in Figure 17, the operation of an IaaS cloud is a cyclical process of consumer requests flowing in and down through the hierarchy, and responses flowing back up to consumers. In addition to virtual machine operations, consumers may directly access data storage servers in the cloud. Even though the aggregate consumer demand peaks and troughs should be more gradual than individual consumer demand peaks and troughs, the cloud will sometimes be underutilized and migration of consumer workloads from computer system to computer system, or even from cluster to cluster, is a strategy that can concentrate consumer workloads on a set of highly utilized machines and allow others to be turned off to save some of the costs of their operation or to allow maintenance activities to be performed."}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\n3.5.1 | Group Attribute Use Metadata... 3.5.1 Group Attribute Use Metadata\n\nIn the course of managing attributes, metadata is applied to subjects and objects as extended attribute information useful for enforcing fine-grained access control policies that incorporate information about the attributes and manage the volumes of data required for enterprise attribute management."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Computer Security Division 2010 Annual Report:\n\nIn fiscal year (FY) 2010, CSD continued to build on its work in se­ curity management and assurance, cryptography and systems se­ curity, identity management and emerging security technologies. CSD played a vital role in both national and international security standard setting. The division continues its leadership role in tech­ nologies and standards for Cloud Computing, Identity Manage­ ment and as a Government Wide Leader and national coordinator for the National Initiative for Cybersecurity Education (NICE). In ad­ dition, this year marked the publication of NIST Interagency Report (NISTIR) 7628, Guidelines for Smart Grid Security, which identifies security requirements applicable to the Smart Grid, security-rele­ vant use cases, logical interface diagrams and interface categories, vulnerability classes abstracted from other relevant cyber security documents, specific issues applicable to the Smart Grid, and priva­ cy concerns. We also continued to provide reference specifications in multiple areas, allowing others to leverage our work to increase the security of their systems and products. tinued to lead, in conjunction with the Government of Canada's Communications Security Establishment, the Cryptographic Module Validation Program (CMVP). The Common Criteria Evaluation and Validation Scheme (CCEVS) and CMVP facilitate security testing of IT products usable by the federal government;\n\nInformation security is an integral element of good management. Information and information systems are critical assets that sup­ port the mission of an organization. Protecting them can be as important as protecting other organizational resources, such as money, physical assets, or employees. In order to protect their as­ sets, organizations need to have assurance that the security tech­ nologies that they invest in can work and allow interoperability, especially in the area of cryptography, as well as management guidance."}], "metadata": {"source": "Computer Security Division 2010 Annual Report", "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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security:\n\n| Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi |\n|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction .........................................................................................................................1 | 1. Introduction .........................................................................................................................1 | 1."}], "metadata": {"source": "Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.7 (NIST 3.1.7)?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\n3.1.7 General Logic Error (CWE-691)\n\nDescription\n\nLogic errors are programming missteps that allow an application to operate incorrectly, but\nusually without crashing."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "nist_control": "3.1.7", "cmmc_practice_id": "AC.L2-3.1.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”:\n\nThe main audiences for this publication are product security officers and security architects at IoT product manufacturers and those in their supply chain; cybersecurity test and evaluation experts; and other stakeholders in the IoT product market. This publication may also help customers or integrators of IoT products who are adopting IoT technologies in their residence or business, especially small business networks, as well as organizations concerned with conformity assessment of IoT products to published guidance. The first keynote was by David Barzilai, VP Sales & Marketing and Co-Founder, Karamba Security, which conducted a survey of Chief Product Security Officers (CPSOs), and their equivalents, to better understand the challenges of this role. David described the role of a CPSO and the challenges they face, especially when dealing with research and development (R&D) teams seeking to balance functionality and security in their products. He cited brand protection through maintaining consumer trust, customer service-level agreement (SLA) requirements, and regulatory compliance as the principal drivers for the creation of the CPSO role. David described a three-fold approach to improve product security and trustworthiness using standards and certifications, which he described as the 'CPSO's best friends'; tools (such as binary analysis for supply-chain security, and vulnerability management systems); and best practices (establishing the manufacturers as being responsible for and monitoring product security). He also identified the reliance on 'massive' supply chains as a huge challenge for addressing product security, noting that it is very hard for manufacturers to impose security best practices on their suppliers. He explained that using software bills of materials (SBOMs) would be very beneficial for creating transparency throughout the supply chain and allow manufacturers to more effectively monitor and address IoT product security risks."}], "metadata": {"source": "Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-07-03 Supersedes NIST SP 800-73-4 (May 2015; updated February 8, 2016) https://doi.org/10.6028/NIST.SP.800-73-4\n\n## How to Cite this NIST Technical Series Publication:\n\nFerraiolo H, Mehta K, Francomacaro S, Chandramouli R, Gupta S (2024) Interfaces for Personal Identity Verification: Part 3 - PIV Client Application Programming Interface. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-73pt3-5. https://doi.org/10.6028/NIST.SP.800-73pt3-5\n\n## Author ORCID iDs\n\nHildegard Ferraiolo: 0000-0002-7719-5999\n\nKetan Mehta: 0009-0001-1191-8656\n\nSalvatore Francomacaro: 0009-0009-0487-2520\n\nRamaswamy Chandramouli: 0000-0002-7387-5858\n\nSarbari Gupta: 0000-0003-1101-0856\n\n## Contact Information\n\npiv\\_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 publications is available at https://csrc.nist.gov/pubs/sp/800/73/pt3/5/final including related content, potential updates, and document history. ## All comments are subject to release under the Freedom of Information Act (FOIA). Interfaces for Personal Identity Verification: Part 3 PIV Client API\n\n## Abstract\n\nFIPS 201 defines the requirements and characteristics of government-wide interoperable identity credentials."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Computer Security Division 2003 Annual Report:\n\ninteroperability and attendant security uses. The Division also added public and private security practices to our Computer Security Resource Center (CSRC) website (http://csrc.nist.gov), held an IT Security Capital Investment Planning Workshop, and updated Special Publication 800-38B specifying the RMAC algorithm to provide example vectors with the AES algorithm as the underlying block cipher. Many more projects and details are included in our report. During the coming year new initiatives will be completed in support of: the Healthcare Information Portability and Accountability Act (HIPAA), integrating security into the capital planning and investment control process, certification and accreditation, the Federal Information Security Management Act (FISMA) directives for Fiscal Year 2004 (FY04), extended outreach initiatives and information security training, awareness and education. Key to success of the program is our ability to interact with a broad constituency-federal and nonfederal, in order to ensure that our program is consistent with national objectives related to or impacted by information security. In addition to risk assessments and security plans, security evaluation also plays an important role in the security accreditation process. It is essential that agency officials have the most complete, accurate, and trustworthy information possible on the security status of their information systems in order to make credible, riskbased decisions on whether to authorize operation of those systems. This information and supporting evidence for system authorization is often developed during a detailed security review of the information system, typically referred to as security certification. Security certification is the comprehensive evaluation of the management, operational, and technical security controls in an information system."}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "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 Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight provide? (Part 3)"}, {"role": "assistant", "content": "March 6, 2024. https://doi.org/10.6028/NIST.IR.8286C-upd1\n\n## Author ORCID iDs\n\nStephen D. Quinn: 0000-0003-1436-684X\n\nNahla Ivy: 0000-0003-4741-422X\n\nMatthew Barrett: 0000-0002-7689-427X\n\nGregory A.\nWitte: 0000-0002-5425-1097\n\n## Contact Information\n\nnistir8286@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8286/c/upd1/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis document is the third in a series that supplements NIST Interagency/Internal Report (NISTIR) 8286, Integrating Cybersecurity and Enterprise Risk Management (ERM). This series provides additional details regarding the enterprise application of cybersecurity risk information; the previous documents, NISTIRs 8286A and 8286B, provided details regarding stakeholder risk direction and methods for assessing and managing cybersecurity risk in light of enterprise objectives. NISTIR 8286C describes how information, as recorded in cybersecurity risk registers (CSRRs), may be integrated as part of a holistic approach to ensuring that risks to information and technology are properly considered for the enterprise risk portfolio. This cohesive understanding supports an enterprise risk register (ERR) and enterprise risk profile (ERP) that, in turn, support the achievement of enterprise objectives."}], "metadata": {"source": "Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\n\n3.1.2."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products:\n\n## A.3.6. Data Protection 1\n\naccess to home networks. They also have robust networking capabilities, giving them utility for a wide range of attacks. Other router product components present their own risks. Backends may aggregate data from one or more customers, making them attractive targets for attackers. Mobile applications may be installed in relatively hostile environments due to malware and other vectors of attack. ISO 31000 [ISO31000] is a foundational resource that developers should use for risk management. NIST's Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy , SP 800-37 Rev. 2 [SP800-37r2] may also be useful guidance for risk management."}], "metadata": {"source": "Recommended Cybersecurity Requirements for Consumer-Grade Router Products", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.......................................................................75 |\n| 5.4.1.\nBusiness Associate Contracts or Other Arrangements (§ 164.314(a)).......................................77 |\n| 5.4.2. Requirements for Group Health Plans (§ 164.314(b))................................................................79 |\n| 5.5.1. Policies and Procedures (§ 164.316(a))......................................................................................81 |\n| 5.5.2. Documentation (§ 164.316(b))...................................................................................................83 |\n| References.......................................................................................................................................85 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................87 |\n| Appendix B. Glossary .......................................................................................................................91 |\n| Appendix C."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements provide? (Part 5)"}, {"role": "assistant", "content": "heir respective organizations. ## Summary of Changes\n\nThe following table details the changes between NISTIR 7511 Revision 4 and NISTIR 7511 Revision 5, which are incorporated in the present document.\n| Date | Type | Change | Page Number |\n|------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| 04/20/2018 | Editorial | Sorted the items listed in Appendix A in alphabetical order | 37 |\n| 04/20/2018 | Editorial | Corrected the section number referenced by SCAP.V.2500.1 | 22 |\n| 04/20/2018 | Substantive | Updated the SCAP.T.2860.1 to match the requirement SCAP.R.2860 | 24 |\n| 04/20/2018 | Editorial | Updated the status of the SP800-126r3, SP800-126A, and SP800-70 to 'Final' | 43 |\n| 04/20/2018 | Substantive | Replaced 'Schematron style sheets' with 'Schematron schemas' to match ISO 19757-3 terminology throughout the document | n/a |\n| 04/20/2018 | Substantive | Updated SCAP.T.1300.2 to include both XSD and Schematron schema for XCCDF component validation."}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Research Report_ User Perceptions of Smart Home Privacy and Security:\n\nAnother said that her biggest concerns were financial: 'bank account because, in that case, you could lose money and they actually wouldn't bring it back. Identity purposes, I don't want my credit being a GLYPH<11> ected because then they can get a whole host of other issues going on' (P17\\_A) ."}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols provide? (Part 2)"}, {"role": "assistant", "content": "ara *«• 9 -, j wnjta '*11 vf,r .r'M ^ ''- w/ / ' *^- • , ri s* >*< ^ 4^SlblW > i Il6 *> » i VI- 7- vwiislt.-^-' '•v '•t^'' ;i*''«4*« ' -r v '*/* •' fliei aiwiiiJWiffc M M: ^HSisjwraH ;3|l^) 5rsi's?j&yr ## Table of Contents | | | | Page | | | | | |--------------|---------------------------------------------|--------------|--------|---------------------------------------------|---------------------------------------------|---------------------------------------------|---------------------------------------------| | Foreword | Foreword | | iii | | | | | | Introduction | Introduction | | vii | | | | | | SDNS | Secure Data Network Security Protocol 3 | System (SP3) | 1 | Secure Data Network Security Protocol 3 | Secure Data Network Security Protocol 3 | Secure Data Network Security Protocol 3 | Secure Data Network Security Protocol 3 | | SDNS | Secure Data Network Security Protocol 4 | System (SP4) | 39 | Secure Data Network Security Protocol 4 | Secure Data Network Security Protocol 4 | Secure Data Network Security Protocol 4 | Secure Data Network Security Protocol 4 | | SDNS | Secure Data Network System Message Security | Protocol | 63 | Secure Data Network System Message Security | Secure Data Network System Message Security | Secure"}], "metadata": {"source": "Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Personnel Security?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\nWhen determining the extent to which the organization automates ISCM, organizations consider potential efficiencies of process standardization that may be gained with automation, and the potential value (or lack of value) of the automated security- related information from a risk management perspective. Additionally, organizations consider intangibles such as the potential value of personnel reassignment and more comprehensive situational awareness.\n\nThis section describes the roles and responsibilities of key participants involved in an organization's ISCM program. Widely varying missions and organizational structures may lead to differences in naming conventions for ISCM-related roles and how specific responsibilities are allocated among organizational personnel (e.g., multiple individuals filling a single role or one\n\nChief Information Officer (CIO). The CIO leads the organization's ISCM program. The CIO ensures that an effective ISCM program is established and implemented for the organization by establishing expectations and requirements for the organization's ISCM program; working closely with authorizing officials to provide funding, personnel, and other resources to support ISCM; and maintaining high-level communications and working group relationships among organizational entities."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8459/final, including related content, potential updates, and document history."}], "metadata": {"source": "Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series", "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 Identification and Authentication?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\nagement is essential for addressing privacy risks related to the loss of the confidentiality, integrity, and availability of individuals' data. For example, data breaches could lead to identity theft.\nHowever, privacy risks can also arise by means that are unrelated to cybersecurity incidents."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to An Introduction to Information Security:\n\n3.2.1 Automated Tools\n\nEven for small multiuser systems, manually reviewing security features may require significant resources."}], "metadata": {"source": "An Introduction to Information Security", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992:\n\n- Establish configuration control for security purposes (Priority A).\n- -Supercomputer sites are high priority.\n- -Distribute/support use of automated security management tools (e.g. COPS).\n- Establish a security perimeter protection capability (Priority B) (e.g. filters, control gateways, Simple Network Management Protocol (SNMP)).\n- Establish security audit information collection and review capability (Priority B).\n\n5. use of privacy enhanced mail for sensitive communication for administration and security officers, Kerberos, Distributed System Security Architecture (DASS);\n6. raising the level of attention with respect to configuration and operation of security relevant portions of the system within a particular site, particularly the domain name service; and\n7. a potpourri of administrative and operational considerations - development of security policies at each center, education of people, careful configuration of the cryptographic parts of each site, fire drills so that timely and effective action can take place when a intrusion is discovered to be in progress, and spending time keeping abreast of the technologies.\n\nCrocker inquired about the memory requirements needed to run Kerberos. Schiller stated the binary file 'rlogin' is required along with a few configuration files. This resides in about 50-60 Kbytes of memory on a VAX. The DES layer can be optimized to gain additional space. At one point, Kerberos was running on a 256K PC. It will presently run on a laptop computer."}], "metadata": {"source": "Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\n3.2.3 DEVELOP ISCM ARCHITECTURE\n\nOrganizations determine how the information will be collected and delivered within and between the tiers as well as external to the organization."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\nList of Abbreviations and Acronyms .........................................................51 | Appendix A. List of Abbreviations and Acronyms .........................................................51 | |\n| Appendix B. Glossary........................................................................................................55 | Appendix B. Glossary........................................................................................................55 | |\n| Appendix C. Additional Resources ..................................................................................58 | Appendix C. Additional Resources ..................................................................................58 | |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Baseline Profile for the Identify Function......................................................................10 | Table 1."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "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 National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\nThis National Institute of Standards and Technology Interagency Report (NISTIR) presents the National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook . The Handbook provides NASA's overall approach to automated information systems security including: program goals and objectives, assignment of responsibilities, risk assessment, foreign national access, contingency planning and disaster recovery, awareness training, procurement, certification, planning, and special considerations for microcomputers. | Paraaraoh | | | Pace |\n|-------------|-------------------------------------------------------|-------------------------------------------------------|--------|\n| | c. | Personnel Screening | 3-6 |\n| | d. | Access Protection and Accountability | 3-6 |\n| | e. | Compliance Assurance | 3-6 |\n| | f | Contingency and Disaster Recovery Plans | 3-7 |\n| | g- | Approval of Methodologies | 3-7 |\n| 303 | Risk | Assessment Process | 3-7 |\n| 304 | Protective Measures to Prevent Misuse and Abuse | Protective Measures to Prevent Misuse and Abuse | 3-10 |\n| 305 | Certification | Process | 3-10 |\n| | a. | New or Modified Applications | 3-11 |\n| | b."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "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 Computer Security Division 2003 Annual Report:\n\nComputer Associates, the Internet Security Task Force, Microsoft, the SANS Institute, and the Carnegie Mellon University CERT Coordination Center. ASSET was first developed and released in 2002.\nThe past year has seen several developments, including a FISMA reporting template and an updated ASSET v1.4 being released in early October 2003. The CSD held several training sessions during 2003, and will continue to hold training sessions in 2004. More updates are under development that will result in a new 2.0 version being released in early 2004."}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\n## Supply Chain\n\nRaw materials are utilized to support the continuous operation of the manufacturing process. Raw materials are typically supplied through a long-term contract established with suppliers and are transported to the facility on a regular basis.\n\nWestman is committed to protecting its trade secrets, including product development, manufacturing processes, product quality, and supply chain management."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "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 Information Integrity?"}, {"role": "assistant", "content": "According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\nby external attackers or the unauthorized access or use of data by employees. Figure 2 shows these types of cybersecurity-related privacy events as the overlap between privacy and cybersecurity risks.\n| Function | Category | | Subcategory |\n|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| appropriate data processing safeguards."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to General Server Security:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guide to General Server Security", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Algorithms and Key Sizes for Personal Identity Verification provide? (Part 5)"}, {"role": "assistant", "content": "osure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\n| | Introduction ...........................................................................................................................1 | Introduction ...........................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| | Purpose and Objectives.................................................................................................."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.10 (NIST 3.4.10)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\n3.4.10, 3."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "cmmc_level": "all", "nist_control": "3.4.10", "cmmc_practice_id": "CM.L2-3.4.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 Media Protection?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories:\n\n| General Support System | 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. [OMB Circular A-130, Appendix III] |\n|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| High-Impact System | An information system in which at least one security objective (i.e., confidentiality, integrity, or availability) is assigned a FIPS 199 potential impact value of high."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\n------------|\n| PR:4.6 | AT-2 | Federal CKMS users and managers shall receive training about the security policies relevant to the FCKMS and the use of the FCKMS in accordance with those policies.\n|\n| PA:4.1 | | The FCKMS Security Policy should specify the following: a) The names of the organization(s) adopting the policy; b) Who (person, title or role) is authorized to approve/modify the policy, c) The impact-levels of the information that is specified in and controlled by the policy, d) The primary data and key/metadata protection services (i.e., data confidentiality, data integrity, source authentication) that are to be provided by the FCKMS, e) The security services (e.g., personal accountability, personal privacy, availability, anonymity, unlinkability, unobservability) that can be supported by the FCKMS, f) Sensitivity and handling restrictions for keys and associated metadata, g) The algorithms and all associated parameters to be used for each impact-level and with each protection service, h) The expected maximum lifetime of keys and metadata for each cryptographic algorithm used, i) The acceptable methods of user/role and source authentication for each information impact-level to be protected by a key and its associated metadata, j) The backup, archiving and recovery requirements for keys and metadata at each information impact-level, k) The roles to be supported by the FCKMS, l) The access control and physical security requirements for the FCKMS's keys and metadata for each impact- level, m) The means and rules for recovering keys and metadata, and n) The communication protocols to be used when protecting sensitive data, keys, and metadata. |"}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "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.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to SRI International_ Improving the Security of Your UNIX System:\n\n3.3.2 | Checklists | 32 |\n| 3. 3.3.2 Checklists\n\nChecklists can be a useful tool for discovering unauthorized changes made to system directories."}], "metadata": {"source": "SRI International_ Improving the Security of Your UNIX System", "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 is CMMC practice IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Standard Security Label for GOSIP_ an Invitational Workshop:\n\n3.5.4 This model maps well to the existing document based world."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions:\n\nThis Standard specifies the Secure Hash Algorithm-3 (SHA-3) family of functions on binary data. Each of the SHA-3 functions is based on an instance of the KECCAK algorithm that NIST selected as the winner of the SHA-3 Cryptographic Hash Algorithm Competition. This Standard also specifies the KECCAKp family of mathematical permutations, including the permutation that underlies KECCAK, in order to facilitate the development of additional permutation-based cryptographic functions.\n\n(modes) of the permutation. In this Standard, the permutation is specified as an instance of a family of permutations, called KECCAKp , in order to provide the flexibility to modify its size and security parameters in the development of any additional modes in future documents.\n\nThe four SHA-3 hash functions differ slightly from the instances of KECCAK that were proposed for the SHA-3 competition [3]. In particular, a two-bit suffix is appended to the messages, in order to distinguish the SHA-3 hash functions from the SHA-3 XOFs, and to facilitate the development of new variants of the SHA-3 functions that can be dedicated to individual application domains."}], "metadata": {"source": "SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to A Threat Analysis on UOCAVA Voting Systems:\n\nOne of the greatest difficulties is the time required to use traditional mail as a mechanism to distribute and receive election material (absentee ballot requests, blank absentee ballots, etc.). In general, the delivery times for postal and military mail to citizens overseas vary greatly depending where the citizen is located. It can take 5 to 10 days for most mail to be delivered to overseas citizens not in the military [25]; and 10 to 14 days for mail to be delivered to military personnel [24]. In addition, uniformed military and overseas citizens may not be at a given physical location for an extended period of time. Given that some jurisdictions finalize their ballots only 30-45 days before an election, using mail to distribute, receive and return election information can be difficult. In some cases the delivery times to distribute blank ballots and return them to local election officials could exceed the window of time between ballot printing and Election Day. This does not take into account the time required for election officials to process and handle blank ballots, or the time required for voters to fill out their ballots and drop them in the mail. Items in the mail are handled by a large number of people. In theory, any of the individuals charged with delivering a registration/request form could open the envelope to obtain personal information. However, this threat is substantially reduced by a variety of factors. Most postal carriers undergo some form of background check. Furthermore, it would be extremely difficult for a small number of malicious individuals to obtain a large amount of information. Most postal employees would only handle a small number of registration/request materials."}], "metadata": {"source": "A Threat Analysis on UOCAVA Voting Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\nUTOMATED CHANGE IMPLEMENTATION The organization employs automated mechanisms to implement changes to the current information system baseline and deploys the updated baseline across the installed base.\n|\n| CM-3(4) | CONFIGURATION CHANGE CONTROL | SECURITY REPRESENTATIVE The organization requires an information security representative to be a member of the [Assignment: organization-defined configuration change control element]. |\n| CM-3(5) | CONFIGURATION CHANGE CONTROL | AUTOMATED SECURITY RESPONSE The information system implements [Assignment: organization-defined security responses] automatically if baseline configurations are changed in an unauthorized manner. |\n| CM-3(6) | CONFIGURATION CHANGE CONTROL | CRYPTOGRAPHY MANAGEMENT The organization ensures that cryptographic mechanisms used to provide [Assignment: organization-defined security safeguards] are under configuration management. |"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset 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 Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for Securing Wireless Local Area Networks (WLANs):\n\nt other networks that are accessible through it, such as internal wired networks reachable from the WLAN. An important principle of WLAN security is to separate WLANs with different security profiles.\nFor example, there should be separate WLANs for external (guest, etc.) and internal use. Devices on an organization's external WLAN should not be able to connect through that WLAN to devices on another of the organization's WLANs. This helps to protect the organization's other networks and devices from external devices and users. Organizations often set up external WLANs primarily to provide Internet access to visitors; such WLANs should be architected so"}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\nPIV enrollment records SHALL maintain an auditable sequence of enrollment events to facilitate binding an applicant to multiple transactions that might take place at different times and locations. 6 These records are generally stored as part of the cardholder's PIV identity account, either as part of the issuer's IDMS or through links to records in other related systems (e.g., card management systems).\n\n- Maintain appeal procedures for those who are denied a credential or whose credentials are revoked.\n- Ensure that only personnel with a legitimate need for access to PII in the PIV system are authorized to access the PII, including but not limited to information and databases maintained for registration and credential issuance. 19\n- Coordinate with appropriate department or agency officials to define consequences for violating privacy policies of the PIV system.\n- Ensure that the technologies used in the department or agency's implementation of the PIV system allow for continuous auditing of compliance with stated privacy policies and with practices governing the collection, use, and distribution of information in the operation of the program.\n- Utilize security controls described in [SP 800-53] to accomplish privacy goals, where applicable.\n- Ensure that the technologies used to implement PIV sustain and do not erode privacy protections relating to the use, collection, and disclosure of PII. Agencies MAY choose to deploy PIV Cards with electromagnetically opaque holders or other technology to protect against any unauthorized contactless access to information stored on a PIV Card."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Computer Security Division 2007 Annual Report:\n\n53 | | Computer Security Division Publications - FY 2007 | 54 | | Ways to Engage Our Division and NIST | 56 |"}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "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 Media Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| FAMILY | FAMILY |\n|-----------------------------------|--------------------------------------|\n| Access Control | Media Protection |\n| Awareness and Training | Personnel Security |\n| Audit and Accountability | Physical Protection |\n| Configuration Management | Risk Assessment |\n| Identification and Authentication | Security Assessment |\n| Incident Response | System and Communications Protection |\n| Maintenance | System and Information Integrity |\n\n17 The Audit and Accountability, Maintenance, Media Protection, and Physical Protection families do not contain enhanced security requirements at this time.\n\n## 3.8 MEDIA PROTECTION"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Metrics and Methodology for Hardware Security Constructs:\n\n| ID | Description |\n|------|----------------------------------------|\n| 26 | Leveraging Race Conditions |\n| 113 | Interface Manipulation |\n| 114 | Authentication Abuse |\n| 122 | Privilege Abuse |\n| 124 | Shared Resource Manipulation |\n| 176 | Configuration/Environment Manipulation |\n| 188 | Reverse Engineering |\n| 192 | Protocol Analysis |\n| 233 | Privilege Escalation |\n| 441 | Malicious Logic Insertion |\n| 624 | Hardware Fault Injection |\n\nIn CAPEC, standard-level attack patterns are a sub-group of meta-level attack patterns that focus on a particular attack methodology or technique. For example, a standard attack pattern can describe a subversion of code-signing mechanisms, which falls under the meta-level attack pattern of privilege escalation. Code signature facilities are used by several programming languages to verify the identity of code and link it to its designated privileges in an appropriate environment. Subverting this mechanism can be instrumental to an attacker escalating privilege. Thus, a standard-level attack pattern describes a specific mechanism for escalating"}], "metadata": {"source": "Metrics and Methodology for Hardware Security Constructs", "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 Approaches for Federal Agencies to Use the Cybersecurity Framework provide? (Part 4)"}, {"role": "assistant", "content": "n determining the risks that are relevant to its mission throughout the operational lifecycle and apply an appropriate type and degree of resources to treat those risks to an acceptable level.\nExamples in this publication will demonstrate the use of the Cybersecurity Framework, the NIST Risk Management Framework (RMF), and other models to evaluate and report agency goals and progress and to inform tailoring activities for managing cybersecurity risk appropriately. Use of a comprehensive cybersecurity risk-based approach, as demonstrated through these examples, supports agencies' activities to meet their concurrent obligations to comply with the requirements of FISMA and Executive Order (EO) 13800. ## Keywords\n\nCybersecurity Framework; Federal Information Security Management Act (FISMA); Risk Management Framework (RMF); Enterprise Risk Management; security and privacy controls. ## Acknowledgments\n\nThe authors would like to thank our advisors and reviewers including Nahla Ivy, Donna Dodson, Adam Sedgewick, Amy Mahn, Matt Scholl, Kevin Stine, Kelley Dempsey, Ron Ross, Jim Foti, Mat Heyman, and Matt Smith. ## Supplemental Content\n\nFor additional information on NIST's cybersecurity programs, projects and publications, visit the Computer Security Resource Center, csrc.nist.gov. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is available at www.nist.gov and www.nist.gov/itl. ## Document Conventions\n\nThe phrase 'federal agencies' in this publication means those agencies responsible for nonnational security-related information in federal systems. FISMA refers to the Federal Information Security Management Act of 2002, as amended. The Federal Information Security Management Act of 2002 was updated through the Federal Information Security Modernization Act of 2014 [1] [2]."}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\n3.2.2 - CHANGE REFERENCE DATA Card Command |\n| DTR-06. 3.2.2 - CHANGE REFERENCE DATA Card Command |\n\n| DTR No: | DTR Description | Spec. 3.2.2 - CHANGE REFERENCE DATA Card Command |\n| DTR-06."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 1_ Overview:\n\n| Attack Step | Attacker Action | Defender Action | |-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1) Gain Internal Entry | The attacker is outside the target boundaries and seeks entry."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "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 CMVP Approved Authentication Mechanisms_ CMVP Validation Authority Requirements for ISO_IEC 19790 Annex E and ISO_IEC 24579 Section 6.17:\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": "CMVP Approved Authentication Mechanisms_ CMVP Validation Authority Requirements for ISO_IEC 19790 Annex E and ISO_IEC 24579 Section 6.17", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Transitioning to the Security Content Automation Protocol (SCAP) Version 2 provide? (Part 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\nStorage technology, just like its computing and networking counterparts, has evolved from traditional storage service types, such as block, file, and object. Specifically, the evolution has taken two directions: one along the path of increasing storage media capacity (e.g., tape, Hard Disk Drives, solid-state drives (SSD)) and the other along the architectural front, starting from direct-attached storage (DAS) to the placement of storage resources in networks accessed through various interfaces and protocols to cloud-based storage resource access, which provides a software-based abstraction over all forms of background storage technologies. Accompanying the architectural evolution is the increase in management complexity, which subsequently increases the probability of configuration errors and associated security threats. This document provides an overview of the evolution of the storage technology landscape, current security threats, and the resultant risks. The main focus of this document is to provide a comprehensive set of security recommendations that will address the threats. The recommendations span not only security management areas that are common to an information technology (IT) infrastructure (e.g., physical security, authentication and authorization, change management, configuration control, and incident response and recovery) but also those specific to storage infrastructure (e.g., data protection, isolation, restoration assurance, and encryption). - Data protection\n- Isolation\n- Restoration assurance\n- Encryption\n\n| Executive Summary...................................................................................................... | Executive Summary...................................................................................................... | Executive Summary......................................................................................................"}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Information Security Handbook_ A Guide for Managers:\n\n- The Federal Information Security Management (FISMA) Act is the primary legislation governing federal information security programs, building upon earlier legislation through added emphasis on the management dimension of information security. - -FISMA delegates to the National Institute of Standards and Technology (NIST) the responsibility to develop detailed information security standards and guidance for federal information systems, with the exception of national security systems. - -FISMA designates to OMB the oversight of federal agencies' information security implementation. - -FISMA provides a comprehensive framework for securing federal government IT resources, including defining key federal government and agency roles and responsibilities, requiring agencies to integrate information security into their capital planning and enterprise architecture processes, requiring agencies to conduct annual information security reviews of all programs and systems, and reporting the results of those reviews to OMB. 2\n- OMB Circular A-130, Management of Federal Information Resources , Appendix III, Security of Federal Automated Information Resources , establishes a minimum set of controls to be included in federal automated information security programs, assigns federal agency responsibilities for the security of automated information, and links agency automated information security programs and agency management control systems. 3\n- Homeland Security Presidential Directive 12 (HSPD-12), released in August 2004, specifies a \"policy for a common identification standard for all Federal employees and contractors.\" 4 HSPD-12 intends to increase identification security and interoperability by standardizing the process to issue a Federal employee or contractor an identification credential, and also by specifying the electronic and physical properties of the credential itself. The HSPD-12 credential is known as the Personal Identity Verification card."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "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 A Review of U.S. and European Security Evaluation Criteria:\n\nTwo types of requirements are delineated for secure processing: (1) specific security feature requirements and; (2) assurance requirements. The latter enable evaluation personnel to determine if the required features are present and functioning as intended.\n\nThe Orange Book forms the basis upon which the National Computer Security Center (NCSC) conducts its commercial computer security evaluation process. This process is focused on commercially produced and supported general-purpose operating system products that meet the needs of government departments and agencies. The evaluation is aimed at off-the-shelf products and is completely separate from any considerations of overall system performance, potential applications, or processing environments. The evaluation can provide a key input to a computer system security approval /accreditation . However, it does not constitute a complete computer system security study. A complete study must consider additional factors dealing with the system in its unique environment, such as its proposed security mode of operation, specific users, applications, data sensitivity, physical and personnel security, administrative security and communications security\n\nThe Orange Book and Red Book criteria do not address all of the security concerns that arise when one actually deploys a system, whether it consists of a single computer or is composed of multiple computer and network products from different vendors. Procedural, physical and personnel safeguards enter into overall system security, and these are only partially addressed by these two documents. System security requires a thorough analysis of the system in question, taking into account not only the ratings of products that might be used to build the system, but also the threats directed against the system. Based on this analysis a security architecture can then be proposed and developed."}], "metadata": {"source": "A Review of U.S. and European Security Evaluation Criteria", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance):\n\n3.1.4 Virtual Contact Interface\n\n| Purpose | Validates that the PUT DATA command cannot be issued through the VCI."}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "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 does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings:\n\n| Logical Component | Component's Function | Function's Relationships to CSF 1.1 Subcategories (and Relationship Properties) | Relationship Explanation |\n|---------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Certificate Authority (CA) | Issues and signs certificates as needed. | Supports (example of) PR.AC- 1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users, and processes | The fact that a credential is signed by a trusted CA provides a mechanism that may be used for enabling the credential to be verified and revoked. |\n| Certificate Authority (CA) | Issues and signs certificates as needed. | Supports (integral to) PR.AC- 6: Identities are proofed and bound to credentials and asserted in interactions | If the device credential is an X.509 certificate (e.g., an IDevID) that is signed by a CA, this certificate binds the device's credential to the device's identity."}], "metadata": {"source": "Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\npplications with the architecture and code types described above. The benefits of this approach for high security assurance and for enabling continuous authority to operate (C-ATO) are also discussed.\nCI/CD pipelines are workflows for taking the developer's source code through various stages, such as building, functional testing, security scanning for vulnerabilities, packaging, and deployment supported by automated tools with feedback mechanisms. For the purpose of this document, the entire set of source code involved in the application environment is classified into five code types:"}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "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 AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface:\n\n3.3.1. 3.3.1."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "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 The Keyed-Hash Message Authentication Code (HMAC) provide? (Part 3)"}, {"role": "assistant", "content": "ed by the message sender to produce a value (the MAC) that is formed by condensing the secret key and the message input. The MAC is typically sent to the message receiver along with the message.\nThe receiver computes the MAC on the received message using the same key and HMAC function as were used by the sender, and compares the result computed with the received MAC. If the two values match, the message has been correctly received, and the receiver is assured that the sender is a member of the community of users that share the key. 4. Approving Authority. Secretary of Commerce. 5. Maintenance Agency. Department of Commerce, National Institute of Standards and Technology, Information Technology Laboratory (ITL). 6. Applicability. This Standard is applicable to all Federal departments and agencies for the protection of sensitive unclassified information that is not subject to Title 10 United States Code Section 2315 (10 USC 2315) and that is not within a national security system as defined in Title 44 United States Code Section 3502(2) (44 USC 3502(2)). The adoption and use of this Standard is available to private and commercial organizations. 7. Specifications. Federal Information Processing Standard (FIPS) 198-1, The KeyedHash Message Authentication Code (HMAC) (affixed). 8. Implementations. The authentication mechanism described in this Standard may be implemented in software, firmware, hardware, or any combination thereof. NIST has developed a Cryptographic Module Validation Program that will test implementations for conformance with this HMAC Standard. Information on this program is available at http://csrc.nist.gov/groups/STM/index.html. Agencies are advised that keys used for HMAC applications should not be used for other purposes. 9. Other Approved Security Functions."}], "metadata": {"source": "The Keyed-Hash Message Authentication Code (HMAC)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Conformance Assessment of Transport Layer Security Implementations:\n\n- (1) Data Integrity,\n- (2) Data Confidentiality,\n- (3) Data Origination Authentication, and\n- (4) Access Control.\n\nThe SP4 standard identifies other security functions on which it depends. These functions include key management, security management, and cryptography. Key management is needed to establish and maintain keying material used by SP4; security management is needed for event reporting and auditing; and cryptography (i.e., employment of specific cryptographic algorithms) is needed to support Data Integrity, Data Confidentiality, and Authentication services. These functions are normally collocated in an end-system, with an SP4 entity.\n\ncomputer system operating environment. The objective of the security evaluation is to perform a technical assessment of the trust properties. Three general security issues that must be addressed are: the confidentiality of the data, the integrity of the data and the system, and the availability of service. The goal or main requirement is to assure that the system behaves according to an organization's security requirements that, in turn, reflect the defined security policy of the organization. To guarantee that this requirement is met, the security functionality of an implementation must work correctly and effectively."}], "metadata": {"source": "Conformance Assessment of Transport Layer Security Implementations", "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 Derived PIV Application and Data Model Test Guidelines:\n\nERNAL AUTHENTICATE), to authenticate an entity to the token (EXTERNAL AUTHENTICATE), and to perform a mutual authentication between the token and an entity external to the token (MUTUAL AUTHENTICATE).\n| • [SP800-157], Appendix B.2 - Derived PIV Application Token Command Interface • [SP800-73], Part 2, Section 3.2.4 - GENERAL AUTHENTICATE Card Command |\n\n| DTR No: | DTR Description | Spec."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Notional Supply Chain Risk Management Practices for Federal Information Systems:\n\n| | 3.1 Roles and Responsibilities for Information and Communication Technology Supply Chain Risk Management _____________________________________________ 12 | 3.1 Roles and Responsibilities for Information and Communication Technology Supply Chain Risk Management _____________________________________________ 12 | 3.1 Roles and Responsibilities for Information and Communication Technology Supply Chain Risk Management _____________________________________________ 12 | | 3.2 Information and Communication Technology Supply Chain Risk Management Implementation Process______________________________________________ 14 | 3.2 Information and Communication Technology Supply Chain Risk Management Implementation Process______________________________________________ 14 | 3.2 Information and Communication Technology Supply Chain Risk Management Implementation Process______________________________________________ 14 | | 4.1 Uniquely Identify Supply Chain | Elements, Processes, and Actors _____________ | 28 | | 4.2 | Limit Access and Exposure within the Supply Chain _______________________ | 31 | | 4.3 | Establish and Maintain the Provenance of Elements, Processes, Tools, and Data | 34 | | 4.4 | Share Information within Strict Limits ___________________________________ | 38 | | 4.5 | Perform Supply Chain Risk Management Awareness and Training ___________ | 45 | | 4.6 | Use Defensive Design for Systems, Elements, and Processes __________________ | 47 | | 4.7 | Perform Continuous Integrator Review __________________________________ | 58 | | 4.8 | Strengthen Delivery Mechanisms _______________________________________ | 61 |"}], "metadata": {"source": "Notional Supply Chain Risk Management Practices for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-09-08\n\n## How to Cite this NIST Technical Series Publication:\n\nChandramouli R, Butcher Z (2023) A Zero-Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Location Environments. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-207A. https://doi.org/10.6028/NIST.SP.800-207A\n\n## Author ORCID iDs\n\nRamaswamy Chandramouli: 0000-0002-7387-5858\n\n## Contact Information\n\nsp800-207A-comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nOne of the basic tenets of zero trust is to remove the implicit trust in users, services, and devices based only on their network location, affiliation, and ownership. NIST Special Publication 800207 has laid out a comprehensive set of zero trust principles and referenced zero trust architectures (ZTA) for turning those concepts into reality. A key paradigm shift in ZTAs is the change in focus from security controls based on segmentation and isolation using network parameters (e.g., Internet Protocol (IP) addresses, subnets, perimeter) to identities. From an application security point of view, this requires authentication and authorization policies based on application and service identities in addition to the underlying network parameters and user identities."}], "metadata": {"source": "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Transitioning the Use of Cryptographic Algorithms and Key Lengths:\n\nSP 800-131A was originally published in January 2011 and revised in 2015. This revision updates the transition guidance provided in the 2015 version; these changes are listed in Appendix B. The most significant difference is the schedule for retiring the Triple Data Encryption Algorithm 5 (TDEA), the inclusion of safe-prime groups for finite field Diffie-\n\n- Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 198-1, July 2008. https://doi.org/10.6028/NIST.FIPS.198-1\n- [FIPS 202] National Institute of Standards and Technology (2015) SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions. (U.S. Department of Commerce, Washington, D.C.), Federal Information Processing Standards Publication (FIPS) 202. https://doi.org/10.6028/NIST.FIPS.202\n- [IG X.Y] Implementation Guidance for FIPS 140-2 and the Cryptographic Module Validation Program, where X.Y is the section number. - [SP 800-38A] Dworkin MJ (2001) Recommendation for Block Cipher Modes of Operation: Methods and Techniques . (National Institute of Standards and Technology, Gaithersburg, Maryland), NIST Special Publication (SP) 800-38A, December 2001. https://doi.org/10.6028/NIST.SP.800-38A\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) 800-38C, May 2004 (includes updates as of 07/20/2007)."}], "metadata": {"source": "Transitioning the Use of Cryptographic Algorithms and Key Lengths", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\ners must be specially designed, developed, and implemented over months or years. Once an automated system is fully operational, the options available to provide computer security are somewhat limited.\nHowever, if security is designed into an automated system, the safeguard options are vastly increased and the safeguard costs over the life of the system are substantially reduced. This is true for computer hardware, system software, and application software. Therefore, it is important for NASA managers to ensure that security is appropriately addressed in all phases of the life cycle for automated systems, especially in the early planning stages. - d. History . In the past, NASA computer security guidance was provided through the following:\n- (1) NASA Handbook (NHB) 2410.1, \"Information Processing Resources Management,\" April 1985."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Computer Security Division 2005 Annual Report:\n\nWe also invite public and private organizations to submit their information security practices to be considered for inclusion on the list of practices maintained on the Web site. Policies and procedures may be submitted to us in any area of information security, including accreditation, audit trails, authorization of processing, budget planning and justification, certification, contingency planning, data integrity, disaster planning, documentation, hardware and system maintenance, identification and authentication, incident handling and response, life cycle, network security, personnel security, physical and environmental protection, production\n\nTo keep pace with the rate of change in emerging technologies, we conduct a large of amount of research in existing and emerging technology areas. Some of the many topics we research include smart card infrastructure and security, wireless and mobile device security, voice over IP security issues, digital forensics tools and methods, access control and authorization management, Internet Protocol security, intrusion detection systems, quantum information system security and quantum cryptography, and vulnerability analyses. Our research helps fulfill specific needs by the Federal government that would not be easily or reliably filled otherwise.\n\nA uthentication of an individual's identity is a fundamental component of physical and logical access control processes. When individuals attempt to access security-sensitive buildings, computer systems, or data, an access control decision must be made. An accurate determination of identity is an important component in making sound access control decisions."}], "metadata": {"source": "Computer Security Division 2005 Annual Report", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Security Segmentation in a Small Manufacturing Environment support CMMC certification?"}, {"role": "assistant", "content": "According to Security Segmentation in a Small Manufacturing Environment:\n\n\n\n## NIST Cybersecurity White Paper NIST CSWP 28\n\n## Security Segmentation in a Small Manufacturing Environment\n\nDr. Michael Powell National Cybersecurity Center of Excellence National Institute of Standards and Technology\n\nJohn Hoyt Aslam Sherule Dr. Lynette Wilcox The MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.CSWP.28\n\nApril 6 , 2023\n\n\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## 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 2023-03-3 0\n\n## How to Cite this NIST Technical Series Publication:\n\nPowell M, Hoyt J, Sherule A, Wilcox L (202 3 ) Security Segmentation in a Small Manufacturing Environment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 28. https://doi.org/10.6028/NIST.CSWP.28\n\n## Author ORCID iDs\n\nDr. Michael Powell: 0000-0002-3922-7435 John Hoyt: 0000-0002-0783-7036 Aslam Sherule: 0000-0002-2003-3817 Dr. Lynette Wilcox: 0000-0003-1246-6505\n\n## Contact Information\n\nmanufacturing\\_nccoe@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). ## Abstract\n\nManufacturers are increasingly targeted in cyber-attacks."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guide to Attribute Based Access Control (ABAC) Definition and Considerations:\n\n| Executive Summary ................................................................................................................... | Executive Summary ................................................................................................................... | Executive Summary ................................................................................................................... | vii |\n|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------|\n| 1. Introduction ............................................................................................................................ | 1. Introduction ............................................................................................................................ | 1. Introduction ............................................................................................................................ | 1 |\n| 1.1 | Purpose and Scope ....................................................................................................... | Purpose and Scope ....................................................................................................... | 1 |\n| 1.2 | Audience ........................................................................................................................."}], "metadata": {"source": "Guide to Attribute Based Access Control (ABAC) Definition and Considerations", "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 Approximate Matching_ Definition and Terminology:\n\n3.3.3 Robustness\n\nRobustness is a measure of the ability of an approximate matching algorithm to find correlation among related objects in the presence of noise and routine transformations. 3.3.3."}], "metadata": {"source": "Approximate Matching_ Definition and Terminology", "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 Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control provide? (Part 5)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security Division 2013 Annual Report:\n\nentity Management | ..............................................................\n42 |\n| Personal Identity Verification (PIV) and FIPS 201 Revision Efforts ...................................................................... | 42 |\n| PIV Program Test Cards ........................................................... | 43 |\n| NIST Personal Identity Verification Program (NPIVP) | .................... 43 |\n| Research in Emerging Technologies | ........................................ 44 |\n| Cloud Computing and Virtualization........................................... | 44 |\n| Mobile Device Security | ............................................................ 46 |\n| Strengthening Internet Security .............................................. | 47 |\n| USGv6: A Technical Infrastructure to Assist IPv6 Adoption............ | 47 |\n| Access Control and Privilege Management.............................. | 48 |\n| Access Control and Privilege Management Research | .................."}], "metadata": {"source": "Computer Security Division 2013 Annual Report", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface:\n\n-2:2021 -Information technology- Abstract Syntax Notation One (ASN.1) - Part 2: Information object specification. (International Organization for Standardization, Geneva, Switzerland) [or as amended].\nAvailable at |\n|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [ISO8825] | International Organization for Standardization/International Electrotechnical Commission (2015) ISO/IEC 8825-1:2015- Information technology -ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) Part 1. (International Organization for Standardization, Geneva, Switzerland) [or as amended]. Available at https://www.iso.org/standard/81420.html |\n| [PKCS1] | Moriarty K, Kaliski B, Jonsson J, Rusch A (2016). Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.2. (Internet Engineering Task Force (IETF)), IETF Request for Comments (RFC) 8017. Available at https://www.rfc-editor.org/rfc/rfc8017 |\n| [SECG] | Certicom (2009) Standards for Efficient Cryptography, SEC 1: Elliptic Curve Cryptography, Version 2.0."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations:\n\nt available version of the document as of the publication of this revision of SP 800-57 Part When later revisions of these referenced documents are available, those versions should referenced instead.\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| CC | Evaluation Criteria for IT Security, International Organization for Standardization, ISO/IEC 15408-1, December 2009. https://www.iso.org/standard/50341.html |\n| CertiPath KR | CertiPath Key Recovery Policy , CertiPath, December 2013."}], "metadata": {"source": "Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Computer Security Division 2007 Annual Report:\n\n- Evaluate security policies and technologies from the private sector and national security systems for potential federal agency use Hosted a growing repository of federal agency security practices, public/private security practices, and security configuration checklists for IT products. In conjunction with the Government of Canada's Communications Security Establishment, CSD leads the Cryptographic Module Validation Program (CMVP). The Common Criteria Evaluation and Validation Scheme (CCEVS) and CMVP facilitate security testing of IT products usable by the federal government. - Solicit recommendations of the Information Security and Privacy Advisory Board on draft standards and guidelines Solicited recommendations of the Board regularly at quarterly meetings on topics such as updates to special publications supporting the FISMA Implementation Project. - Provide outreach, workshops, and briefings Conducted ongoing awareness briefings and outreach to our customer community and beyond to ensure comprehension of guidance and awareness of planned and future activities. We also held workshops to identify areas our customer community wishes to be addressed, and to scope guidelines in a collaborative and open format. - Satisfy annual NIST reporting requirement Produced an annual report as a NIST Interagency Report (IR). The 2003-2006 Annual Reports are available via the Web or upon request. I T products make claims as to their functional and/or security capabilities. When protecting sensitive data, government agencies need to have a minimum level of assurance that a product's stated security claim is valid. There are also legislative restrictions regarding certain types of technology, such as cryptography, that require federal agencies to use only tested and validated cryptographic modules."}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers:\n\n| Field Name | Description |\n|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Target Operational Environment | The IT product's operational environment, such as Standalone, Managed, or Custom (with description, such as Specialized Security-Limited Functionality, Legacy, or United States Government). Generally only applicable for security compliance/vulnerability checklists. |\n| Checklist Type | The type of checklist, such as Compliance, Vulnerability, and Specialized. |\n| Checklist Installation Tools | Describes the functional tools required to use the checklist to configure the system, if they are not included with the checklist. |\n| FIPS 140-2 Compliance | Whether the product can operate in a FIPS 140-2 validated mode (yes or no)."}], "metadata": {"source": "National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\n- 1) Agency management should ensure that computer security has the highest level of management involvement. This involvement is also important in the computer security planning process. Computer security benefits from the multiple perspectives of and input from agency IRM, computer security, and functional, user, and applications personnel\n- 2) Agency management should identify and describe the security needs of their systems which contain sensitive information. - 3) Agency management should recognize the importance of computer security and its required planning. This recognition should be aggressively communicated to their staffs, perhaps using their computer security and awareness training programs as one of the vehicles. - 4) Agencies should incorporate computer security planning with other information systems planning activities. - 5) Agencies should consider the protection requirements for integrity and availability on an equal basis with that of confidentiality. - 6) Agencies should assess risks and select and implement realistic controls throughout the system life cycle. This involves awareness of technology changes with regard system hardware and software. This awareness also requires a knowledge of new technology and new methods for protecting and recovering from system threats. - 7) Atjcncic:; should implement certification and accreditation programs."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "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 Risk Assessment?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1:\n\n| Executive Summary................................................................................................................... 1 | Executive Summary................................................................................................................... 1 | Executive Summary................................................................................................................... 1 | Executive Summary................................................................................................................... 1 |\n|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ........................................................................................................................ | 1. Introduction ........................................................................................................................ | 1. Introduction ........................................................................................................................"}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Existing Application-Specific Key Derivation Functions:\n\nTo protect the integrity of communications, a session key, SKEY , is derived from a secret authorization value, Auth , that is a secret key shared between the TPM and the application. An HMAC-PRF is used to produce the SKEY as follows:\n\n- (1) The TPM KDF is performed in the context of a TPM session (i.e. performed between a TPM and an application with a shared authorization value.)"}], "metadata": {"source": "Recommendation for Existing Application-Specific Key Derivation Functions", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n1 While agencies are required to follow NIST guidance in accordance with OMB policy, there is flexibility within NIST's guidance in how agencies apply the guidance. Unless otherwise specified by OMB, the 800-series guidance documents published by NIST generally allow agencies some latitude in the application. Consequently, the application of NIST guidance by agencies can result in different security solutions that are equally acceptable, compliant with the guidance, and meet the OMB definition of adequate security for federal information systems. When assessing federal agency compliance with NIST guidance, auditors, evaluators, and assessors should consider the intent of the security concepts and principles articulated within the particular guidance document and how the agency applied the guidance in the context of its specific mission responsibilities, operational environments, and unique organizational conditions.\n\nProvide system functionality testing and/or validation procedures to ensure that the system is operating correctly. This section may be combined with the Data Testing section if procedures test both the functionality and data validity. Teams or persons responsible for each procedure should be identified. An example of a functional test for a low-impact system may be logging into the system and running a report or performing a transaction to see if the system is operating correctly. Detailed functionality test procedures may be provided in Appendix E, System Validation Test Plan.\n\n- ƒ Keystroke-level recovery steps;\n- ƒ System installation instructions from tape, CD, or other media;\n- ƒ Required configuration settings or changes;\n- ƒ Recovery of data from tape and audit logs; and\n- ƒ Other system recovery procedures, as appropriate."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines for the Use of PIV Credentials in Facility Access:\n\n| 1. | Introduction........................................................................................................................... 1 |\n|------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | Background....................................................................................................................1 |\n| 1.2 | Purpose and Scope.........................................................................................................1 |\n| 2. | Characteristics of PIV Implementations ............................................................................ 3 |\n| 2.1 | Benefits of the Complete Implementation.....................................................................3 |\n| 2.2 | Qualities of the Complete Implementation....................................................................4 |\n| 2.3 | Interoperability Qualities...............................................................................................5 |\n| 2.4 | Infrastructure Requirements ..........................................................................................6 |\n| 3. | Threat Environment............................................................................................................."}], "metadata": {"source": "Guidelines for the Use of PIV Credentials in Facility Access", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 1_ Overview:\n\ntion of Volume 1.......................................................................................................3 |\n| 2.\nOverview of an Automated Security Control Assessment Process .......................................4 |\n| 2.1 Prerequisites to Automated Security Control Assessment......................................................4 |\n| 2.2 Automating the Test Assessment Method................................................................................5 |\n| 2.2.1 Terms for Referring to Assessment Objects......................................................................6 |\n| 2.3 Factors for Determining When to Trust Automated Ongoing Assessments ...........................6 |\n| 2.4 An Automated Security Control Assessment Program: ISCM................................................7 |\n| 2.5 Preparing for Automated Security Control Assessments........................................................9 |\n| 3."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nThe SCAP Validation Program uses several reference implementation tools that aid in the development and testing of SCAP products. The SCAP Validation (SCAPVal) Tool may be used for checking the correctness of SCAP data streams; SCAPVal is required during formal SCAP validation testing. Reference implementation tools may be used to process SCAP content; these tools are not required during formal SCAP validation testing. The SCAP Validation Tool and reference implementation tools are discussed in more detail below."}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements", "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.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to SRI International_ Improving the Security of Your UNIX System:\n\n3.2.2 | The showmount Command | 28 |\n| 3. 3.2.2 The showmount Command\n\nThe showmount command [Sun88a, 1764] can be used on an NFS file server to display the names of all hosts that currently have something mounted from the server."}], "metadata": {"source": "SRI International_ Improving the Security of Your UNIX System", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface:\n\n3.2.1. 3.2.1. 3.2.1."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "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 Media Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Building a Cybersecurity and Privacy Learning Program:\n\nacy training. Some organizations may need to require visitors and/or guests to sign acceptable use policies if they allow them any type of system access, including use of wireless network connections.\n- All users: This is also known as 'general workforce training' and includes regularly scheduled (often annual but preferably more frequent) cybersecurity and privacy training for all system users, including personnel without access to the system. An analysis of this audience's training requirements should include reviewing the performance of previous program elements and any new organizational requirements. - Privileged access account holders: These are personnel with additional responsibilities who are trusted to perform cybersecurity- or privacy-relevant functions that ordinary users are not authorized to perform. They will require additional training in order to be provided with privileged access accounts. When identifying privileged access account holders, consider:\n- o Whether new systems have been implemented or are planned and the rights and privileges associated with privileged access accounts\n- o Whether the list of participants with system owners is complete and whether new rights and privileges are required\n- o Whether any of these systems have been moved to the cloud and require new training\n- Staff with significant cybersecurity and/or privacy responsibilities training: Some positions require role-based training for staff with significantly specialized responsibilities. This type of training includes:\n- o Specialized or customized training on specific products, networks, systems, applications, or information\n- o Work role tasks and activities, such as incident response procedures, oversight responsibilities, or identity management\n- o Reskilling and upskilling programs\n- o Learning that helps the employee perform their work tasks"}], "metadata": {"source": "Building a Cybersecurity and Privacy Learning Program", "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 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report:\n\ngement, 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| | Introduction: Workshop Objective, Participants, and Agenda.......................................1 |\n|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Workshop Session Highlights and Summaries................................................................5 |\n| HPC | Architecture and Security Posture ........................................................................5 |\n| | HPC Operator Security Experience...............................................................................6 |\n| | Risk Management Framework Development, Implementation, and Assessment.........7 |\n| 2.3.1."}], "metadata": {"source": "3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report", "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 Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n| Function Unique Identifier | Function | Category Unique Identifier | Category | |------------------------------|------------|------------------------------|--------------------------------------------------------| | ID | Identify | ID.AM | Asset Management | | ID | Identify | ID.BE | Business Environment | | ID | Identify | ID.GV | Governance | | ID | Identify | ID.RA | Risk Assessment | | ID | Identify | ID.RM | Risk Management Strategy | | ID | Identify | ID.SC | Supply Chain Management | | PR | Protect | PR.AC | Identity Management, Authentication and Access Control | | PR | Protect | PR.AT | Awareness and Training | | PR | Protect | PR.DS | Data Security | | PR | Protect | PR.IP | Information Protection Processes and Procedures | | PR | Protect | PR.MA | Maintenance | | PR | Protect | PR.PT | Protective Technology | | DE | Detect | DE.AE | Anomalies and Events | | DE | Detect | DE.CM | Security Continuous Monitoring | | DE | Detect | DE.DP | Detection Processes | | RS | Respond | RS.RP | Response Planning | | RS | Respond | RS.CO | Communications | | RS | Respond | RS.AN |"}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n1.3.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n\n2.3.2. Authentication Process\n\n3.2."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n3.3.4 Technology Limitations\n\nAlthough network-based IDPSs offer extensive detection capabilities, they do have some significant limitations. 3.3.4 Technology Limitations\n\nAlthough wireless IDPSs offer robust detection capabilities, they do have some significant limitations."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "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 Physical Protection?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n| Subcategory | Applicability to the Ground Segment | References | |---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| | ID.AM-1 : Physical devices and systems within the organization are inventoried | Organizations should document and maintain an inventory of the components, to include cloud-based resources, that reflect the current system."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Control Baselines for Information Systems and Organizations provide? (Part 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Recommendation for Existing Application-Specific Key Derivation Functions provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-135 Revision 1\n\n## Recommendation for Existing Application-Specific Key Derivation Functions\n\nQuynh Dang\n\nComputer Security Division Information Technology Laboratory\n\n## C O M P U T E R S E C U R I T Y\n\nDecember 2011\n\n\n\nU.S. Department of Commerce\n\nJohn Bryson, Secretary\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary for Standards and Technology and Director\n\n## Abstract\n\nCryptographic keys are vital to the security of internet security applications and protocols. Many widely-used internet security protocols have their own applicationspecific Key Derivation Functions (KDFs) that are used to generate the cryptographic keys required for their cryptographic functions. This Recommendation provides security requirements for those KDFs. KEY WORDS: Cryptographic key, shared secret, Diffie-Hellman (DH) key exchange, hash function, Key Derivation Function (KDF), Hash-based Key Derivation Function, Randomness Extraction, Key expansion, Pseudorandom Function (PRF), HMAC, ANS X9.42-2001, ANS X9.63-2001, IKE, SSH, TLS, SRTP, SNMP and TPM. ## Acknowledgements\n\nThe author gratefully appreciates the comments and contributions of the many reviewers in various Federal agencies and the public. In particular, the author would like to thank Elaine Barker, William E. Burr, Lily Chen, Tim Polk, Tim Hall, Scott Rose and Hugo Krawczyk. ## NIST SP 800-135, Revision 1\n\n## Table of Contents\n\n| 1 | Introduction........................................................................................ | Introduction........................................................................................"}], "metadata": {"source": "Recommendation for Existing Application-Specific Key Derivation Functions", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ................................................................................................... 2\n1.2 TARGET AUDIENCE .................................................................................................................. 3\n1.3 ORGANIZATIONAL RESPONSIBILITIES......................................................................................... 3\n1.4 RELATIONSHIP TO OTHER PUBLICATIONS ................................................................................... 5\n1.5 REVISIONS AND EXTENSIONS .................................................................................................... 5\n1.6 PUBLICATION ORGANIZATION .................................................................................................. 5\nCHAPTER TWO THE FUNDAMENTALS ............................................................................................ 7\n2.1 REQUIREMENTS AND CONTROLS .............................................................................................. 7\n2.2 CONTROL STRUCTURE AND ORGANIZATION .............................................................................. 8\n2.3 CONTROL IMPLEMENTATION APPROACHES ............................................................................. 11\n2.4 SECURITY AND PRIVACY CONTROLS ......................................................................................... 13\n2.5 TRUSTWORTHINESS AND ASSURANCE ..................................................................................... 14\nCHAPTER THREE THE CONTROLS ................................................................................................. 16\n3.1 ACCESS CONTROL .................................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nParticipants indicated topics that their security awareness programs addressed via training courses, events, or other communications in the past 1 - 2 years. Figure 9 shows the security awareness topics and percentages of programs addressing those topics. All participants' programs covered the topic of social engineering, and over 90% addressed passwords and authentication, malware, and privacy topics. Security considerations when installing or updating software was the least covered topic but still addressed by 64% of programs.\n\n- 'I do consult with members of the SOC [Security Operations Center] to see if there's anything glaring that I need to include in my training each year.' (N09)\n- 'Also working with the help desk, just what type of problems our users encounter that are related to security issues.' (S05)\n- 'Being tied directly to the cybersecurity policy team has made it easier because the awareness team always has whatever the latest guidance is and can push that out very quickly.' (D03)\n- 'We've worked closely with the information security officials' (N08)\n- 'I'm located in the chief information security office, and there are…divisions in that office that provide a wide range of cybersecurity services to the Department. And those managers have responsibilities for things such as identity management, internet response, data loss prevention. So, within any year, I reach out to those stakeholders to ask, 'What's important for the user to understand about cybersecurity awareness? What do you want to talk to the customer about? What kind of behaviors are you seeing that you want us to help encourage them to do or not to do?.' (D01)\n- 'Build relationships with offices within your organization- Incident Response, Help Desk,…FISMA Compliance.' (Q24)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security and Trust Considerations for Digital Twin Technology provide? (Part 3)"}, {"role": "assistant", "content": "itions between states of these entities. This report discusses the concept and purpose of digital twin technology and describes its characteristics, features, functions, and expected operational uses.\nThis report also discusses both traditional and novel cybersecurity challenges presented by digital twin technology as well as trust considerations in the context of existing NIST guidance and documents. ## Keywords\n\ncomputer cybersecurity; control; digital twin technology; instrumentation; real-time command; real-time monitoring; simulation; standards; testing; trust; use case scenarios. ## 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. ## Audience\n\nThis publication is intended for anyone who wants to understand the underlying technology and envisioned capabilities of digital twin technology. It is particularly applicable to Standards Developing Organizations (SDOs) and implementers of digital twin technology. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL."}], "metadata": {"source": "Security and Trust Considerations for Digital Twin Technology", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories:\n\n| EXECUTIVE SUMMARY.........................................................................................................VII | EXECUTIVE SUMMARY.........................................................................................................VII | EXECUTIVE SUMMARY.........................................................................................................VII | | |------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| | 1.0 | INTRODUCTION..................................................................................................................1 | INTRODUCTION..................................................................................................................1 | | | 1.1 | Purpose and Applicability ......................................................................................................1 | Purpose and Applicability ......................................................................................................1 | | | 1.2 | Target Audience.....................................................................................................................1 | Target Audience.....................................................................................................................1 | | | 1.3 | Relationship to Other Documents ..........................................................................................1 | Relationship to Other Documents ..........................................................................................1 | | | 1.4 | Organization of this Special Publication................................................................................2 | Organization of this Special Publication................................................................................2 | | | 2.0 | PUBLICATION OVERVIEW...............................................................................................4 | PUBLICATION OVERVIEW...............................................................................................4 | | | 2.1 | Agencies Support the Security Categorization Process .........................................................4 | Agencies Support the Security Categorization Process .........................................................4 | | | 2.2 | Value to Agency Missions, Security Programs and IT Management ....................................4 | Value to Agency Missions, Security Programs and IT Management ....................................4 | | | 2.3 | Role in the System Development Lifecycle...........................................................................5 | Role in the System Development Lifecycle...........................................................................5 | | | 2.4 | Role in the Certification and Accreditation Process ..............................................................5 | Role in the Certification and Accreditation Process ..............................................................5 | | | 2.5 | Role in the NIST Risk Management Framework...................................................................6 | Role in the NIST Risk Management Framework...................................................................6 | | | 3.0 | SECURITY CATEGORIZATION OF INFORMATION AND"}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs provide?"}, {"role": "assistant", "content": "\n\n## Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs\n\nAnoop Singhal Ximming Ou\n\n## NIST Interagency Report 7788\n\nSecurity Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs\n\n## Anoop Singhal Ximming Ou\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nAugust 2011\n\n\n\nU.S. Department of Commerce\n\nRebecca M. Blank, Acting Secretary\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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 Internal Report discusses ITL's research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Interagency Report 7788 # pages (August 2011)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to Bluetooth Security:\n\nBluetooth wireless technology and associated devices are susceptible to general wireless networking threats, such as denial of service (DoS) attacks, eavesdropping, man-in-the-middle (MITM) attacks, message modification, and resource misappropriation. They are also threatened by more specific attacks related to Bluetooth wireless technology that target known vulnerabilities in Bluetooth implementations and specifications. Attacks against improperly secured Bluetooth implementations can provide attackers with unauthorized access to sensitive information and unauthorized use of Bluetooth devices and other systems or networks to which the devices are connected."}], "metadata": {"source": "Guide to Bluetooth Security", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\n1. Name of the project, and a description of the purpose and scope.\n2. Mission requirement the system is designed to satisfy.\n3. Estimated costs (capital investment and operations) for each fiscal year 1989-1993.\n4. Description of input (typewritten text, invoices, receipts, forms, drawings, etc.). If practical, attach examples of documents that illustrate the various types of information that\n5. will be captured. For example, if documents contain both text and image, provide a sample of that type of document.\n5. Description of the origin of the input including both the type and location of organizations supplying the documents and the technology that the supplier uses to create the documents, if known\n6. Description of the conversion and input process, including scanning system, authentication procedures, use of outside contractors, quality control and data loading procedures.\n7. Proposed accuracy of stored image (150 dots per inch, 200 dots per inch, etc.).\n8. Storage format for images (Group 4 FAX, etc.).\n9. Description of proposed work station for retrieval (including screen resolution, number and size of screens, communications speed and protocol, zoom, local storage capacity, etc.).\n10. Volume of stored images (in pages and bytes) to be captured initially, total volume online each year FY 1989-1993, volume removed from online access (archived or destroyed) each year FY 1989-1993.\n11. Response time for online document retrieval.\n12. Brief description of the operation of the indexing and storage system (index keys, searching techniques, off-the-shelf system, etc. )\n13. A description of unique functions, capabilities, or performance standards (such as large format hardcopy output, grey scale image enhancement, etc.) required by this system that will make it different from commercially available systems.\n14. The name and telephone number of a point of contact who can provide more information."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters:\n\n3.2.3 | 3. 3.2.3 Protecting Personal Voter Information\n\nVoter registration applications and absentee ballot requests contain personally identifiable information, such as names, addresses, and identification numbers. 3.2.3, forms developed by state and local jurisdictions for voter registration and ballot requests should not ask for information that is not required or desired by jurisdictions."}], "metadata": {"source": "Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters", "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 Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out provide? (Part 5)"}, {"role": "assistant", "content": "| INTRODUCTION | |\n| | A. | Document Purpose. Scope and Audience | 1-1 1-1 |\n| | B.\n| Not a Substitute for Good Computer Security Management | 1-1 |\n| | 0. | Security is not a One-time Activity | 1-2 |\n| | D. | Obtaining Computer Security Services: In-house vs. Contracting Out | .... 1-2 |\n| | E. | Overview of the Document | 1-2 |\n| | F. | The Evolving Nature of this Document | 1-4 |\n| | G. | Conventions in this Document | 1-5 |\n| | | Sources of Information | 1-5 |\n| | H. | Additional | |\n| II. | COMPUTER | COMPUTER | |\n| | | SECURITY PROGRAM MANAGEMENT | Il-l |\n| | A. | Overview | Il-l |\n| | B. | Development of a Computer Security Program | 11-2 |\n| | C. | Program Assessment | 11-7 |\n| III. | | APPLICATION SECURITY | Ill-l |\n| | A. | Overview | Ill-l |\n| | B. | Computer Security and Privacy Plan Preparation | |\n| | | (lAW OMB CIR 90-08) | III-4 |\n| | C."}], "metadata": {"source": "Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\nDe-Identifcation . . . . . | 18 |\n| 3.2. | Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n| Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| | 3.2.1. | Probability of Re-Identifcation . . . . | 21 |\n| | | 3.2.2. Adverse Impacts of Re-Identifcation . | 24 |\n| | | 3.2.3. Impacts Other Than Re-Identifcation | 26 |\n| | | 3.2.4. Remediation . . . . . . . . . . . . . . . | 27 |\n| | | Data Life Cycle | |\n| 3.3. . . | 3.3. . . | . . . . . . . . . . . . . . . . | 27 |\n| 3.4. Data-Sharing Models . | 3.4."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Fiscal Year 2021 Cybersecurity and Privacy Annual Report:\n\n| Foreword........................................................................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| Focus Area 1: Cryptographic Standards and Validation................................................................ | 2 |\n| Focus Area 2: Cybersecurity Measurement........................................................................................ | 6 |\n| Focus Area 3: Education and Workforce.............................................................................................. | 9 |\n| Focus Area 4: Identity and Access Management............................................................................. | 12 |\n| Focus Area 5: Privacy Engineering......................................................................................................... | 15 |\n| Focus Area 6: Risk Management ............................................................................................................ | 18 |\n| Focus Area 7: Trustworthy Networks.................................................................................................... | 25 |\n| Focus Area 8: Trustworthy Platforms.................................................................................................... | 31 |\n| ITL Leadership and Participation in National and International Standards Programs...... | 35 |\n| Opportunities to Engage with the NIST on Cybersecurity and Privacy................................... | 37 |"}], "metadata": {"source": "Fiscal Year 2021 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\n| Category | Subcategory and Selected Informative References | Ransomware Application | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | PR.DS-5: Protections against data leaks are implemented ISO/IEC 27001:2013 A.12.1.3, A.17.2.1 NIST SP 800-53 Rev."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report) provide? (Part 2)"}, {"role": "assistant", "content": "ecurity and Privacy Plan (CSPP) review effort that was conducted in response to the Act by a joint team from NIST and NSA in 1989. The report also discusses future directions for implementing the Act.\nThe Computer Security Act of 1987 (the Act) has further increased our growing awareness that information and information resources are integral to the functioning of government -and that their protection is fundamental, not peripheral to, the government serving the public trust. We applaud and support the efforts undertaken under the Act and welcome the opportunity to further serve in this area. We would like to acknowledge, congratulate, and thank the many individuals and agencies that took the time and effort to seriously examine their computer security programs and plans. We are proud of the vital role that our organizations play in supporting the Act's goals. We look forward to continued cooperation between our organizations in carrying out the spirit of the Computer Security Act to better serve the federal community and, ultimately, the public. \n\n\n\nNational Computer Systems Laboratory National Institute of Standards and Technology\n\nNational Computer Security Center National Security Agency\n\nWe appreciate the opportunity to participate in this historic chapter of promoting the protection of federal information and information technology resources. We take pride in the manner in which our organizations and staffs worked together and in what this project has started. We thank those who participated in this initial journey and who contributed to our collective learning about the challenges we face and how we address them. \n\n\n\nJr."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop:\n\n- In his opinion, IoT security has not received enough attention, in both consumer and organizational contexts. He noted that the increasing interconnection of systems of all types increases attack surfaces and expands the threat profile. - He identified three core activities that the Office of Management and Budget (OMB) performs that are particularly relevant to federal information system security:\n- o Overseeing the implementation of Federal Information Security Management Act (FISMA) for non-National Security Systems; he noted that in doing this OMB works closely with the Department of Defense (DoD) and the Director of National Intelligence (DNI) to present consistent guidance across the federal space including the DoD and the intelligence community (IC). - o Overseeing the implementation of cybersecurity policies and standards. He noted that OMB has been taking a more active oversight role and seeking to assist federal organizations in meeting their FISMA responsibilities. - o Ensuring agencies comply with government-wide cybersecurity guidance and legislation, including Binding Operational Directives and Emergency Directives from the Department of Homeland Security's (DHS) Cybersecurity and Infrastructure Security Agency (CISA). - He stated that the scope of 'Federal Information systems includes IoT devices', adding 'I don't think we've had enough conversation on that.' He expressed concern that IoT devices are seen as less impactful or less risky, and cited an example of a networked traffic sign being used as an entry point for a cyber-attack as a 'wake-up call' to the range of concerns that IoT raises. - He emphasized that OMB's work in cybersecurity is guided by a risk management philosophy. He described a 'high-value asset' program intended to assist agencies in identifying and protecting their high-value information system and data, and share solutions across agencies."}], "metadata": {"source": "Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop", "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 Personnel Security?"}, {"role": "assistant", "content": "According to Information Security Handbook_ A Guide for Managers:\n\nin coordination with the other senior agency officials, reports annually to the agency head on the effectiveness of the agency information security program, including the progress of remedial actions.\n- Heading an office with the mission and resources to assist in ensuring agency compliance with information security requirements;\n- Periodically assessing risk and magnitude of the harm resulting from unauthorized access, use, disclosure, disruption, modification, or destruction of information and information systems that support the operations and assets of the agency;\n- Developing and maintaining risk-based, cost-effective information security policies, procedures, and control techniques to address all applicable requirements throughout the life cycle of each agency information system to ensure compliance with applicable requirements;\n- Facilitating development of subordinate plans for providing adequate information security for networks, facilities, and systems or groups of information systems;\n- Ensuring that agency personnel, including contractors, receive appropriate information security awareness training;\n- Training and overseeing personnel with significant responsibilities for information security with respect to such responsibilities;\n- Periodically testing and evaluating the effectiveness of information security policies, procedures, and practices;\n- Establishing and maintaining a process for planning, implementing, evaluating, and documenting remedial action to address any deficiencies in the information security policies, procedures, and practices of the agency;\n- Developing and implementing procedures for detecting, reporting, and responding to security incidents;\n- Ensuring preparation and maintenance of plans and procedures to provide continuity of operations for information systems that support the operations and assets of the agency; and\n- Supporting the agency CIO in annual reporting to the agency head on the effectiveness of the agency information security program, including progress of remedial actions."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "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 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 System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Cryptographic Key Generation:\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": "Recommendation for Cryptographic Key Generation", "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 Security Analysis of First Responder Mobile and Wearable Devices:\n\nScott Ledgerwood Public Safety Communications Research Division Communications Technology Laboratory\n\nJaydee L. Griffith Institute for Telecommunication Sciences National Telecommunications and Information Administration\n\nFirst and foremost, the authors wish to gratefully acknowledge the contributions of the public safety professionals offering their time and rich expertise to this study. Additionally, information gleaned from the Association of Public-Safety Communications Officials (APCO), specifically Mark Reddish, was invaluable. The authors also would like to thank their colleagues who reviewed drafts of this document and contributed to its technical content including John Beltz, Michael Ogata, Andrew Regenscheid, and Nelson Hastings of NIST; Vincent Sritapan of DHS S&T."}], "metadata": {"source": "Security Analysis of First Responder Mobile and Wearable Devices", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Glossary of Computer Security Terminology:\n\nindependent technical personnel according to an acceptable standard of proof such that the level of security protection is identified with regard to a procedure, program, system component, or system.\n(OPNAVINST 5239.1 A)\n\n| eavesdropping | The unauthorized interception of information- bearing emanations through the use of methods other than wiretapping. (FIPS PUB 39; AR 380-380) |\n|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| economic assessment | A detailed study of security measures, their operational and technical feasibility, and their costs and benefits. Economic assessment aids in planning and selecting security measures. (AFR 205-16, AFR 700-10) |\n| electromagnetic emanations | Signals transmitted as radiation through the air and through conductors. (FIPS PUB 39; AR 380-380) |\n| electronic funds transfer (EFT) | Electronic funds transfer refers to the movement of value (money) from one party to another by electronic means."}], "metadata": {"source": "Glossary of Computer Security Terminology", "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 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 is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Notional Supply Chain Risk Management Practices for Federal Information Systems:\n\n3.2.2 Conduct Initial Planning\n\nThe procurement official (under the Contracting role in Section 3."}], "metadata": {"source": "Notional Supply Chain Risk Management Practices 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 does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Glossary of Computer Security Terminology:\n\ny, or integrity ofcomputer resources. Computer abuse includes fraud, embezzlement, theft, malicious damage, unauthorized use, denial ofservice, and misappropriation. Levels of computer abuse are:\n- a.\nMinorAbuse - Acts that represent managementproblems (printing calendars or running games), but do not impact system availability for authorized applications;\n- b. Major Abuse - Unauthorized use (possibly criminal), resulting in denial ofservice, multiple instances of minor abuse, or waste;"}], "metadata": {"source": "Glossary of Computer Security Terminology", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines for API Protection for Cloud-Native Systems:\n\n- Impacts on business operations (e.g., damage to equipment and personnel, the creation of fake orders that require human effort to sort and remove)\n- Impacts on customer relationships (e.g., scalpers automatically buying inventory to relist at a higher price elsewhere)\n- Infrastructure co-opted for abuse or harassment (e.g., multi-factor authentication fatigue attacks, where an attacker triggers text spam to a user's phone via an SMS 2factor authentication system [9])\n- Unplanned expenses (e.g., consuming far more of a third-party service than planned by satisfying requests made by a malicious user)"}], "metadata": {"source": "Guidelines for API Protection for Cloud-Native Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Security Perspective on the Web3 Paradigm provide? (Part 3)"}, {"role": "assistant", "content": "tegration of these developing technologies may present novel security challenges, so this paper presents security considerations that should be addressed when considering Web3 technology and adoption.\n## Keywords\n\nblockchain; cryptocurrency; data; decentralized; decentralized identity; non-fungible tokens; smart contracts; tokens; Web3. ## 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. ## Audience\n\nThis publication is designed for readers with little or no knowledge of Web3 technology who wish to understand how it works at a high level. It is not intended to be a technical guide. The discussion of the technology provides a conceptual understanding, and some examples, figures, and tables are simplified to fit the audience. ## 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": "A Security Perspective on the Web3 Paradigm", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-218\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\nRecommendations for Mitigating the Risk of Software Vulnerabilities\n\nMurugiah Souppaya Karen Scarfone Donna Dodson\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-218\n\n\n\n## NIST Special Publication 800-218\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\nRecommendations for Mitigating the Risk of Software Vulnerabilities\n\nMurugiah Souppaya Computer Security Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nDonna Dodson*\n\n* Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-218\n\nFebruary 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for API Protection for Cloud-Native Systems:\n\n.................9 |\n| 2.6.1. Input Validation..........................................................................................................................11 |\n| 2.6.2.\nMalicious Input Protection.........................................................................................................11 |\n| 2.7.1. Gateways Straddle Boundaries ..................................................................................................12 |\n| 2.7.2. Requests With a Service Identity But No User Identity..............................................................12 |\n| 2.7.3. Requests With a User Identity But No Service Identity..............................................................13 |\n| 2.7.4. Requests With Both User and Service Identities........................................................................14 |\n| 2.7.5. Reaching Out to Other Systems .................................................................................................15 |\n| 2.7.7. Identity Canonicalization............................................................................................................16 |\n| 3. Recommended Controls for APIs...................................................................................................17 |\n| 3.1.1. Basic Pre-Runtime Protections...................................................................................................18 |\n| 3.1.2. Advanced Pre-Runtime Protections ...........................................................................................19 |\n| 3.2.1. Basic Runtime Protections..........................................................................................................20 |"}], "metadata": {"source": "Guidelines for API Protection for Cloud-Native 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 Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\n| Audience.........................................................................................................\n| 2 |\n| | Document Structure........................................................................................ | 3 |\n| 2. Overview of Manufacturing Systems ...................................................................4 | 2. Overview of Manufacturing Systems ...................................................................4 | |\n| CSF Manufacturing Profile Overview ...................................................................5 | CSF Manufacturing Profile Overview ...................................................................5 | |\n| 4. CSF Manufacturing Profile Implementation Approach.......................................6 | 4. CSF Manufacturing Profile Implementation Approach.......................................6 | |\n| 5."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "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 Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings:\n\n| 1 | Introduction ............................................................................................................1 | Introduction ............................................................................................................1 |\n|--------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| 2 | 1.2 | About the IoT Cybersecurity Colloquium......................................................... 1 |\n| | Summary and Key Takeaways..............................................................................3 | Summary and Key Takeaways..............................................................................3 |\n| | 2.1 | Defining the Internet of Things........................................................................ 3 |\n| | 2.2 | IoT Cybersecurity and Privacy Risks .............................................................. 3 |\n| | 2.3 | IoT-Specific Risks ..........................................................................................."}], "metadata": {"source": "Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings", "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 NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\nAn organization completes its Current Profile by indicating which Category and Subcategory outcomes from the remaining Functions are being achieved. If an outcome is partially achieved, noting this fact will help support subsequent steps by providing baseline information. Informed by the activities under Identify and Govern, such as organizational privacy values and policies, organizational risk tolerance, and privacy risk assessment results, an organization completes its Target Profile focused on the assessment of the Categories and Subcategories describing its desired privacy outcomes. An organization also may develop its own additional Functions, Categories, and Subcategories to account for unique organizational risks. It may also consider influences and requirements of external stakeholders such as\n\nSince either a Current or Target Profile can be used to generate a prioritized list of privacy requirements, these Profiles can also be used to inform decisions about buying products and services. By first selecting outcomes that are relevant to its privacy goals, an organization then can evaluate partners' systems, products, or services against this outcome. For example, if a device is being purchased for environmental monitoring of a forest, manageability may be important to support capabilities for minimizing the processing of data about people using the forest and should drive a manufacturer evaluation against applicable Subcategories in the Core (e.g., CT.DP-P4: system or device configurations permit selective collection or disclosure of data elements )."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "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 Application Container Security Guide:\n\nアプリの脆弱性 | ..........................................................................................................................................18 | | 3.4.5 未承認コンテナ ..........................................................................................................................................18 | | | 3.5 ホスト OS のリスク ..........................................................................................................................................18 | | | 3.5.1 大きなアタックサーフェス | ........................................................................................................................18 |"}], "metadata": {"source": "Application Container Security 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 Awareness and Training?"}, {"role": "assistant", "content": "According to Building Secure Microservices-based Applications Using Service-Mesh Architecture:\n\n- Circuit breaker: Large-scale distributed systems, no matter how they are architected, have one defining characteristic-they provide many opportunities for small, localized failures to escalate into system-wide catastrophic failures. The Service Mesh must be designed to safeguard against these escalations by shedding load and failing quickly when the underlying systems approach their limits. Circuit breaking involves setting a threshold for the failed responses from an instance of a microservice and cutting off forwarding requests to that instance when the failure is above the threshold (e.g., when the circuit breaker trips). This mitigates the possibility of cascading failure and allows for time to analyze logs, implement the necessary fix, and push an update for the failing instance. Thus, circuit breaking is a temporary measure that prevents total disruption to responses for service requests. The service requests will be restored to the instance once the service is responsive.\n- Rate limiting (throttling): The rate of requests coming into a microservice must be limited to ensure continued availability of service for all clients.\n- Blue/green deployments: When a new version of a microservice is deployed, requests from customers using the old version can be redirected to the new version using the API gateway that can be programmed to maintain awareness of the locations of both versions.\n- Canary releases: Only a limited amount of traffic is initially sent to a new version of a microservice since the correctness of its response or performance metric under all operating scenarios is not fully known. Once sufficient data is gathered about its operating characteristics, then all of the requests can be proxied to the new version of the microservice."}], "metadata": {"source": "Building Secure Microservices-based Applications Using Service-Mesh Architecture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Computer Security Division 2012 Annual Report:\n\n|\n| Security Outreach and Integration Group................ | 5 |\n| Security Testing, Validation, and Measurement Group...\n| 6 |\n| The Computer Security Division Implements the Federal Information Security Management Act of 2002......................................................7 | |\n| CSD's Programs/Projects for FY2012..................8 | |\n| CSD Work in National and International Standards....."}], "metadata": {"source": "Computer Security Division 2012 Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Codes for Identification of Federal and Federally-Assisted Organizations:\n\nProtection Agency | | | Field Activities of the Department of Defense | | 97F1 | American Forces Information Service | | 9758 | Defense Prisoner of War/Missing Personnel Office | | 97AU | Defense Technology Security Administration | | 9748 | Defense Human Resources Activity | | 97F2 | Department of Defense Education Activity | | 97F6 | Office of Economic Adjustment | | 97F5 | Washington Headquarters Services | | 9760 | TRICARE Management Activity |"}], "metadata": {"source": "Codes for Identification of Federal and Federally-Assisted Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security Division 2010 Annual Report:\n\nIssued fifteen final NIST Special Publications (SP) that addressed management, operational and technical security guidance in areas such as, securing WiMax wireless networks, secure con­ tent automation protocols, protection of personally identifi­ able information, Bluetooth security, and deployment of Secure Domain Name System deployment. In addition, eight draft SPs were issued for public comment for cryptographic key deploy­ ment and security configuration management among other topics;\n\n- Continued the successGLYPH(cmap:df00)ul collaboration with the OGLYPH(cmap:df00) GLYPH(cmap:df00) i ce oGLYPH(cmap:df00) the Director of National Intelligence, Committee on National Security Systems and the Department of Defense to estab­ lish a common foundation for information security across the federal government, including a consistent process for selecting and specifying safeguards and countermeasures (i.e., security controls) for federal information systems;\n- Provided assistance to agencies and private sector: Conducted ongoing, substantial reimbursable and non-reim­ bursable assistance support, including many outreach ef­ forts such as the Federal Information Systems Security Edu­ cators' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSM Forum), and the Small Business Corner;\n- As part oGLYPH(cmap:df00) its contribution to the Smart Grid initiative, CSD released NIST IR 7628, Guidelines for Smart Grid Cyber Security, in August 2010;\n- Reviewed security policies and technologies GLYPH(cmap:df00)rom the private sector and national security systems for potential federal agency use: hosted a growing repository of federal agency security practices, public/private security practices, and security configuration checklists for IT products."}], "metadata": {"source": "Computer Security Division 2010 Annual Report", "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 Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology provide? (Part 3)"}, {"role": "assistant", "content": "h to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. Submit comments on this publication to:\n\ncyberhygiene@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nEnterprise patch management is the process of identifying, prioritizing, acquiring, installing, and verifying the installation of patches, updates, and upgrades throughout an organization. Patching is more important than ever because of the increasing reliance on technology, but there is often a divide between business/mission owners and security/technology management about the value of patching."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 The NIST Cybersecurity Framework (CSF) 2.0:\n\n- o 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 - o PR.AA-06: Physical access to assets is managed, monitored, and enforced commensurate with risk - Awareness and Training (PR.AT): The organization's personnel are provided with cybersecurity awareness and training so that they can perform their cybersecurity-related tasks - o 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 - o PR.AT-02: Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind - Data Security (PR.DS): Data are managed consistent with the organization's risk strategy to protect the confidentiality, integrity, and availability of information - o PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected - o PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected - o PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected - o PR.DS-11: Backups of data are created, protected, maintained, and tested - Platform Security (PR.PS): The hardware, software"}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Proceedings of the Workshop of the Federal Criteria for Information Technology Security:\n\nblems. The component group also felt that the document organization should be re-examined and the Federal Criteria should be minimized. They also would have liked to have seen the fimctional packages.\nThe component group also felt that the Federal Criteria should limit the requirement statements to accepted engineering practices rather than research ideas (but not exclude adding new accepted ideas), but the global issues groi^ didn't see how this statement applied to the Federal Critoia - the only research idea that they could remember was real time audit alarms. The component group identified several items that they felt were not well accepted. These included the requirements for both functional and penetration testing as defined in the Federal CMteria since they are significantly different from the ITSEC and TCSEC, the requirement for using 'high-level synchronization,' the allowance for layering violation, and the use of multi-threaded tasks for Trusted Computing Base (TCB) structuring."}], "metadata": {"source": "Proceedings of the Workshop of the Federal Criteria for Information Technology Security", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Computer Security Log Management:\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. 21 Some organizations, particularly smaller ones, may choose to have a single log management infrastructure used throughout the enterprise. For most organizations, a single infrastructure is not feasible for any of several reasons, including limitations on the scalability of a single infrastructure, logging occurring on logically or physically separate networks, concern about robustness (e.g., having a single infrastructure means that a failure of that infrastructure affects logging throughout the organization), and interoperability issues among log generators and infrastructure components. Communications between log management infrastructure components typically occur over an organization's regular networks because the hosts generating log data may be located throughout the organization's networks. However, a physically or logically separate logging network can be used, particularly for getting logs from key devices (e.g., firewalls and network intrusion detection systems that often transfer large amounts of log data) and for transferring log data between log servers."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n...............................................................................17 | |\n| 4.1.5.\n| Authentication Mechanisms...................................................................................17 | |\n| Enterprise Mobile Security Technologies...................................................................18 | Enterprise Mobile Security Technologies...................................................................18 | |\n| 4.2.1. | Enterprise Mobility Management............................................................................18 | |\n| 4.2.2. | Mobile Application Management............................................................................20 | |\n| 4.2.3. | Mobile Threat Defense...........................................................................................21 | |\n| 4.2.4. | Mobile App Vetting.................................................................................................22 | |\n| 4.2.5. | Virtual Mobile Infrastructure ...................................................................................22 | |\n| 4.2.6."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Information Security Guide for Government Executives:\n\nOver time, information security efforts may need to be revisited because of changes in agency mission, operational requirements, threats, environment, or deterioration in the degree of compliance. Periodic assessments and reports on activities can be a valuable means of identifying areas of noncompliance. Reminding employees of their responsibilities and demonstrating management's commitment to the security program are key to maintaining effective security within the constantly changing information security environment. Executives should ensure a life-cycle approach to compliance by monitoring the status of their programs to ensure that:\n\nImplementing a robust information security program within the federal government is challenging. Federal executives have to contend with constantly changing technology, multiple compliance requirements, increasing complexity of information security, and changing threats. However, the executive can navigate these challenges and accomplish an organization's critical information security goals."}], "metadata": {"source": "Information Security Guide for Government Executives", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\nThis guide provides general implementation guidance (Volume 1) and example proof-of-concept solutions demonstrating how available open-source and commercial off-the-shelf (COTS) products could be implemented in manufacturing environments to satisfy the requirements in the Cybersecurity Framework (CSF) Manufacturing Profile [8] Low Impact Level. A manufacturing system could be classified as Low potential impact if the loss of integrity, availability, or confidentiality could be expected to have a limited adverse effect on manufacturing operations, manufactured product, assets, brand image, finances, personnel, the general public, or the environment. A limited adverse effect means that, for example, the loss of integrity, availability, or confidentiality might:\n\nMany small and medium-sized manufacturers have expressed challenges in implementing a standards-based cybersecurity program. This guide provides general implementation guidance (Volume 1) and example proof-of-concept solutions demonstrating how available open-source and commercial off-the-shelf (COTS) products could be implemented in manufacturing environments to satisfy the requirements in the Cybersecurity Framework (CSF) Manufacturing Profile [8] Low Impact Level. A manufacturing system could be classified as Low potential impact if the loss of integrity, availability, or confidentiality could be expected to have a limited adverse effect on manufacturing operations, manufactured product, assets, brand image, finances, personnel, the general public, or the environment. A limited adverse effect means that, for example, the loss of integrity, availability, or confidentiality might:\n\nThe Cybersecurity Program document establishes guidelines and principles for initiating, implementing, maintaining, and improving information security management of the organization. It is a documented set of the organization's security policies, procedures, guidelines and standards."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "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 Derived PIV Application and Data Model Test Guidelines provide? (Part 5)"}, {"role": "assistant", "content": "interface, data object container size and access requirements. + Enable issuers of Derived PIV Credentials to ensure that Derived PIV data objects conform to the requirements specified in SP 800-157.\n+ Enable developers and issuers to develop self-tests as part of the development effort and issuance process. + Enable entities performing conformance tests on Derived PIV Applications and Derived PIV data objects to develop tests that cover the test suite provided in this document. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.10 (NIST 3.1.10)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.1.10. 3.1.10."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "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.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Managing the Security of Information Exchanges:\n\n3.3.1 Maintain Clear Lines of Communication... 3.3.10 Review the Continued Need for the Information Exchange ... 3.3.1 Maintain Clear Lines of Communication\n\nIt is critical that the organizations participating in an information exchange maintain clear lines of communication and communicate regularly."}], "metadata": {"source": "Managing the Security of Information Exchanges", "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 guidance does 2017 NIST_ITL Cybersecurity Program Annual Report provide?"}, {"role": "assistant", "content": "\n\n## ANNUAL REPORT 2017 NIST/ITL CYBERSECURITY PROGRAM\n\n\n\n## THIS PAGE IS INTENTIONALLY LEFT BLANK\n\n## ANNUAL REPORT 2017\n\n## NIST/ITL CYBERSECURITY PROGRAM\n\n## PATRICK O'REILLY, EDITOR\n\nComputer Security Division Information Technology Laboratory\n\n## KRISTINA RIGOPOULOS, EDITOR\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nCO-EDITORS: Larry Feldman Greg Witte G2, Inc. Annapolis Junction, Maryland\n\nTHIS PUBLICATION IS AVAILABLE FREE OF CHARGE FROM https:/ /doi.org/10.6028/NIST.SP.800-203\n\nJULY 2018\n\n\n\nU.S. DEPARTMENT OF COMMERCE Wilbur L. Ross, Jr., Secretary\n\nNATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY\n\nWalter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## AUTHORITY\n\nThis publication has been developed by the National Institute of Standards and Technology (NIST) in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3541 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": "2017 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms:\n\n- Trust : 'The confidence one element has in another that the second element will behave as expected.' [3]\n- Trusted : An element that another element relies upon to fulfill critical requirements on its behalf. - Trusted boot : A system boot where aspects of the hardware and firmware are measured and compared against known good values to verify their integrity and thus their trustworthiness. - Trustworthy : Worthy of being trusted to fulfill whatever critical requirements may be needed. 1\n\nThere are security and privacy concerns with allowing unrestricted container deployment orchestration. A common desire is to only use cloud servers physically located within the same country as the organization, or physically located in the same country as the origin of the information. Whenever multiple container deployments are present on a single cloud server, there is a need to segregate those deployments from each other so that they do not interfere with each other, gain access to each other's sensitive data, or otherwise compromise the security or privacy of the containers. NIST IR 8320A, Hardware-Enabled Security: Container Platform Security Prototype [1] provides an overview of challenges organizations may face when using cloud-based container workloads, as well as techniques to improve the security of cloud computing and accelerate the adoption of cloud computing technologies by establishing an automated hardware root-of-trust method for enforcing and monitoring platform integrity and geolocation restrictions for cloud servers. The motivation behind this use case is to build upon the stages of NIST IR 8320A and implement additional techniques that leverage hardware roots of trust in server platforms. The integrity and location data of each host are leveraged in the orchestration and protection of workloads, as well as providing workloads access to specific data."}], "metadata": {"source": "Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to 2016 NIST_ITL Cybersecurity Program Annual Report:\n\n3 | BACKGROUND INFORMATION OF ANNUAL REPORT.................................................................................................................."}], "metadata": {"source": "2016 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cell Phone Forensic Tools_ an Overview and Analysis:\n\norcement Standards (OLES), the U. S. Department of Defense, Federal Bureau of Investigation (FBI), U.S. Secret Service, the U.S. Immigration and Customs Enforcement (BICE), and other related agencies.\n·\n\nThe scenarios define a set of prescribed activities used to gauge the capabilities of the forensic tool to recover information from a phone, beginning with connectivity and acquisition and moving progressively toward more interesting situations involving common applications, file formats, and device settings. The scenarios are not intended to be exhaustive or to serve as a formal product evaluation. However, they attempt to cover a range of situations commonly encountered when examining a device (e.g., data obfuscation, data hiding, data purging) and are useful in determining the features and functionality afforded an examiner."}], "metadata": {"source": "Cell Phone Forensic Tools_ an Overview and Analysis", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\n| Target Audience..............................................................................................\n| 2 |\n| | 1.3 | Relationship to Other Publications.................................................................. | 3 |\n| | 1.4 | Document Conventions................................................................................... | 3 |\n| | 1.5 | Publication Organization................................................................................."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nScott Rose Wireless Networks Division Communications Technology Laboratory\n\nFor additional information on NIST's Cybersecurity programs, projects, and publications, visit the Computer Security Resource Center. Information on other efforts at NIST, the Information Technology Laboratory (ITL) and Communications Technology Laboratory (CTL) is also available. Zero trust related information is also found on the zero trust topic page.\n\nNational Institute of Standards and Technology Attn: Wireless Networks Division, Communications Technology Laboratory 100 Bureau Drive (Mail Stop 8920) Gaithersburg, MD 20899-8920"}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nFiles and keychain elements are both protected by one of a number of access control keys, which are also encrypted in a way that incorporates the user's device passcode. The passcode"}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\n...............................11 |\n| 2.5.1. Speaker Viewpoints....................................................................................................................11 |\n| 2.5.2.\nKey Highlights .............................................................................................................................13 |\n| 3. Summary and Road Ahead ...........................................................................................................15 |\n| Appendix A. Workshop Agenda........................................................................................................16 |\n| List of Figures |\n| Fig. 1. Components for securing microelectronics................................................................................1 |\n| Fig. 2. Distribution of workshop participants.......................................................................................2 |"}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Physical Protection?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management:\n\n----------------------------------------------------------------------|\n| 2) Initiate Attack Internally | The attacker is inside the boundary and initiates attack on some assessment object internally.\nExamples include: User opens spear phishing email or clicks on attachment; user installs unauthorized software or hardware; unauthorized personnel gain physical access to restricted facility. | Block or Limit Internal Access: Prevent or minimize access of potentially unauthorized/compromised devices to trusted network resources; Reduce amount of time unauthorized devices are present before detection. |"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\n3.1.3 Infection of Malware and Ransomware | ... 3.1.3 Infection of Malware and Ransomware\n\nMalware is the general term for any program that is designed to damage, disrupt, or provide means to compromise a device."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Recommendation for Block Cipher Modes of Operation_ Methods for Format-Preserving 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": "Recommendation for Block Cipher Modes of Operation_ Methods for Format-Preserving 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 System and Communications Protection?"}, {"role": "assistant", "content": "According to Computer Security Training & Awareness Course Compendium:\n\n|-------------------------------------------------------------------------------------|-----------------------------------------------------------------------| | DATA CENTER RECOVERY PLANNING (M2040) | 20 | | DATA COMMUNICATIONS SECURITY | 28 | | DATA SECURITY PLANNING: STRATEGIES FOR EFFECTIVE INFORMATION SECURITY (W9898) | 22 | | DATA SECURITY PLANNING | 68 | | DATABASE SECURITY SEMINAR | 65 | | DETECTING AND PREVENTING COMPUTER FRAUD | 11 | | DEVELOPING COMPUTER SECURITY POLICIES & PROCEDURES | 28 | | DISASTER RECOVERY PLANNING | 70 | | DISASTER RECOVERY PLANNING: STRATEGIES TO DEVELOP & MAINTAIN PROVABLE | DISASTER RECOVERY PLANNING: STRATEGIES TO DEVELOP & MAINTAIN PROVABLE | | RECOVERY CAPABILITY (W9912) | 20 | | EDI: New Frontiers For Auditors | 56 | | EDP AUDITING - CIS 433 | 78 | | EDP CONCEPTS FOR BUSINESS | 6 | | EDP AUDITING: THE FIRST STEP | 52 | | EXECUTIVE AIS SECURITY BRIEFING | 8 | | FEDERAL AIS COMPUTER SECURITY REQUIREMENTS | 4 | | FUNDAMENTALS OF COMPUTER SECURITY FOR FEDERAL INFORMATION SYSTEMS | 64 | | HOW TO MANAGE AN INFORMATION SECURITY PROGRAM: A GUIDE FOR NEWLY APPOINTED MANAGERS | 23 | | IMPLEMENTING & MANAGING A COMPUTER SECURITY PROGRAM | 19 | | IMPLEMENTING AND TESTING THE DISASTER RECOVERY PLAN | 88"}], "metadata": {"source": "Computer Security Training & Awareness Course Compendium", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\n| | | | | | | | PAGE | PAGE | PAGE | PAGE | PAGE | PAGE | PAGE | PAGE | PAGE | PAGE | |-------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|------------------------------------|------------------------------------|--------|--------|--------|--------|--------|--------|--------|--------|--------|--------| | ABSTRACT | ABSTRACT | ABSTRACT | | | | | i | i | i | i | i | i | i | i | i | i | | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | EXECUTIVE SUMMARY | | | | | ii | ii | ii | ii | ii | ii | ii | ii | ii | ii | | LIST | OF APPENDICES | OF APPENDICES | | | | | v | v | v | v | v | v | v | v | v | v | | 1 | INTRODUCTION | | | | | | | | | | | | | | | | | | 1.1 | Development of Security Technology | Development of Security Technology | Development of Security Technology | Development of Security Technology | Development of Security Technology | 1-1 | 1-1 | 1-1 | 1-1 | 1-1 | 1-1 | 1-1 | 1-1 | 1-1 | 1-1 | | | 1.2 |"}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "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 Guidelines on Electronic Mail Security:\n\n| 5.3 Checklist for Securing the Mail Server Operating System.......................................5-7 | 5.3 Checklist for Securing the Mail Server Operating System.......................................5-7 | | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| | Securing Mail | Servers and | Content................................................................................6-1 | | 6.1 Hardening the Mail Server Application.....................................................................6-1 | 6.1 Hardening the Mail Server Application.....................................................................6-1 | | | 6.1.1 | Securely Installing the Mail Server | ...............................................................6-1 | | 6.1.2 | Configuring Operating System and Mail Server Access Controls | ................6-1 | | | Protecting Email from Malware................................................................................6-3 | | | 6.2 6.2.1 | Malware Scanning........................................................................................6-5 | | | 6.2.2 | Content Filtering | ...........................................................................................6-9 | | 6.2.3 | User Awareness | .........................................................................................6-12 | | 6.3 | Blocking Spam-Sending Servers | ...........................................................................6-13 | | 6.4 | Authenticated Mail Relay | .......................................................................................6-14 | | 6.5 | Secure Access.......................................................................................................6-14 | | | 6.6 | Enabling Web Access............................................................................................6-15 | | | 6.7 | Checklist for Securing Mail Servers and Content | ..................................................6-16 | | Implementing a Secure Network Infrastructure ............................................................7-1 | Implementing a Secure Network Infrastructure ............................................................7-1 | | | 7.1 | Network Composition and Structure | ........................................................................7-1 | | | 7.1.1 Inadvisable Network Layout | .........................................................................7-1 | | 7.1.2 | Demilitarized Zone........................................................................................7-1 | | | | 7.1.4 Management Network | ..................................................................................7-5"}], "metadata": {"source": "Guidelines on Electronic Mail 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 Level 2 require for Physical Protection?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\nA.03.04.05[01]: physical access restrictions associated with changes to the system are defined and documented."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications:\n\n| The sum of the log 2 distances between matching L- bit templates, i.e., the sum of the number of digits in the distance between L- bit templates. See Sections 2.9 and 3.9.\n|\n| π | 3.14159… unless defined otherwise for a specific test. |\n| σ | The standard deviation of a random variable = ( ) ∫ - f ( x )dx x 2 µ . |\n| σ 2 | The variance of a random variable = (standard deviation) 2 . |\n| s obs | The observed value which is used as a statistic in the Frequency test. |\n| S n | The n th partial sum for values X i = {-1, +1}; i.e., the sum of the first n values of X i . |\n| Σ | The summation symbol. |\n| Φ | Standard Normal Cumulative Distribution Function (see Section 5.5.3). |\n| ξ j | The total number of times that a given state occurs in the identified cycles. See Section 2.15 and 3.15. |\n| X i | The elements of the string consisting of ± 1 that is to be tested for randomness, where X i = 2 ε i - 1. |"}], "metadata": {"source": "A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications", "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 Information Integrity?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\nThe Minimum Security Requirements for Multi-User Operating Systems (MSR) document provides basic commercial computer system security requirements applicable to both government and commercial organizations. These requirements include technical measures that can be incorporated into multi-user, remote-access, resource-sharing, and information-sharing computer systems. The MSR document was written from the prospective of protecting the confidentiality and integrity of an organization's resources and promoting the continual availability of these resources. The MSR presented in this document form the basis for the commercially oriented protection profiles in Volume II of the draft Federal Criteria for Information Technology Security document (known as the Federal Criteria). The Federal Criteria is currently a draft and supersedes this document. | SECTION | SECTION | SECTION | PAGE |\n|-----------|--------------|-------------------------------------------------------------|--------|\n| | Abstract | | ii |\n| 1."}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Threat Analysis on UOCAVA Voting Systems provide? (Part 2)"}, {"role": "assistant", "content": "| EXECUTIVE SUMMARY..........................................................................................................\n1 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1 INTRODUCTION................................................................................................................. | 1 INTRODUCTION................................................................................................................. | 1 INTRODUCTION................................................................................................................. | 3 |\n| 1.1 | 1.1 | SCOPE .............................................................................................................................."}], "metadata": {"source": "A Threat Analysis on UOCAVA Voting Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\n|\n| Encryption.....................................................................................................\n| 26 |\n| Data Loss Prevention.................................................................................... | 26 |\n| Media Sanitization......................................................................................... | 27 |\n| Event Logging............................................................................................... | 27 |\n| Forensics ...................................................................................................... | 28 |\n| 7. Capabilities Mapping to Manufacturing Profile .................................................30 | |\n| 8. Laboratory Environment | Overview.....................................................................60 |\n| Process-based Manufacturing System ........................................................."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Quick Start Guide for Populating Mobile Test Devices:\n\n---------------------------|\n| Profile information, Status updates, personal messages, etc. | Facebook/Facebook messenger | Profile related data (picture, bio), Status updates, personal messages, etc.\n|\n| | Twitter | Profile related data (picture, bio), Tweets, personal messages, etc. |\n| | LinkedIn | Profile related data (picture, bio), personal messages, etc. |\n| | Instagram | Profile related data (picture, bio), Posted pictures, videos, etc. |"}], "metadata": {"source": "Quick Start Guide for Populating Mobile Test Devices", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Computer Security Log Management:\n\nMuch of this information, particularly for applications that are not used through unencrypted network communications, can only be logged by the applications, which makes application logs particularly valuable for application-related security incidents, auditing, and compliance efforts. However, these logs are often in proprietary formats that make them more difficult to use, and the data they contain is often highly context-dependent, necessitating more resources to review their contents. Communications between log management infrastructure components typically occur over an organization's regular networks because the hosts generating log data may be located throughout the organization's networks. However, a physically or logically separate logging network can be used, particularly for getting logs from key devices (e.g., firewalls and network intrusion detection systems that often transfer large amounts of log data) and for transferring log data between log servers. During a widespread malware incident or other network-based attack, regular networks might be unstable or unavailable. Another motivation for using a separate logging network is protecting log data on the organization's regular networks from eavesdropping. If a separate logging network is not used, logging communications on the regular network could be protected using additional security controls, such as data encryption. Another benefit of having a separate logging network is protecting those components that are only used for log management from attacks. - -Log compression is storing a log file in a way that reduces the amount of storage space needed for the file without altering the meaning of its contents. Log compression is often performed when logs are rotated or archived. - -Log reduction is removing unneeded entries from a log to create a new log that is smaller. A similar process is event reduction , which removes unneeded data fields from all log entries."}], "metadata": {"source": "Guide to Computer Security Log 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 Level 2 require for Maintenance?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n| . . . . . . . . . . . . . . . . . . . . . . . . . . 3 |\n| 1.3.3 New Features . . . . . . . . . | . . . . . . . . . . . . . . . . . . . . . .\n4 |\n| 1.3.4 Deprecated and Removed Features . . . . . | . . . . . 4 |\n| 1.3.5 FIPS 201 Version Management . . . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 |\n| 1.3.6 Section Number Stability . . . | . . . . . . . . . . . 5 |\n| 1.4 Document Organization . . . . . . . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 |\n| 2. Common Identification, Security, and Privacy Requirements . . . . . . . . . | 2. Common Identification, Security, and Privacy Requirements . . . . . . . . . |\n| 2.1 Control Objectives . . . . . . | . 7 . . . . . . . . . . . . . . . . . . . . . . . . . 7 |\n| 2.2 Credentialing Requirements . . . . . . . . . . | . . . . . . . . . . . 8 |\n| 2.3 Biometric Data Collection for Background Investigations . . . | . . . . . . . . . . . . . . . 9 |\n| 2.4 Biometric Data Collection for PIV Card . . . . . . . . . . | . . . . . . . . . . . . . . . . . . 9 |\n| 2.5 Biometric Data Use . . . | . . . . . . . . . . . . . . . . . . . 10 |\n| 2.6 PIV Enrollment Records . . . . . | . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Guide to Secure Web Services:\n\n3.1.1 | Service Chaining ... 3.1.1 Service Chaining\n\nSometimes, a service provider may not be able to perform the actions that a user or requester wishes it to perform, but it knows of a remote Web service that can. 3.1.1 C and C++\n\nThere are many cases where Java, ."}], "metadata": {"source": "Guide to Secure Web Services", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\nl innovation, the Framework is technology neutral. The Framework relies on a variety of existing standards, guidelines, and practices to enable critical infrastructure providers to achieve resilience.\nBy relying on those global standards, guidelines, and practices developed, managed, and updated by industry, the tools and methods available to achieve the Framework outcomes will scale across borders, acknowledge the global nature of cybersecurity risks, and evolve with technological advances and business requirements. The use of existing and emerging standards will enable economies of scale and drive the development of effective products, services, and practices that meet identified market needs. Market competition also promotes faster diffusion of these technologies and practices and realization of many benefits by the stakeholders in these sectors."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "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 Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.14. Digital Injection Prevention and Forged Media Detection . . . . . . . . .\n\n• Cryptographic verification of the source and integrity of digital evidence or\n\n2. Based on the results of its privacy risk assessment, the CSP SHALL document the\nmeasures it takes to maintain the disassociability, predictability, manageability,\nconfidentiality, integrity, and availability of any personal information it collects\nor processes.4 In determining such measures, the CSP SHOULD apply relevant\nguidance and standards, such as the NIST Privacy Framework [NIST-Privacy] and\nNIST SP 800-53 [SP800-53]."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guidelines for Securing Wireless Local Area Networks (WLANs):\n\n|  SP 800-30, Risk Management Guide for Information Technology Systems |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n|  Draft SP 800-30 Revision 1, Guide for Conducting Risk Assessments  SP 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach  SP 800-40 Version 2.0, Creating a Patch and Vulnerability Management Program  SP 800-41 Rev. 1, Guidelines on Firewalls and Firewall Policy  SP 800-48 Rev."}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "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 Information Security Handbook_ A Guide for Managers provide? (Part 3)"}, {"role": "assistant", "content": "thank the many people who assisted with the development of this handbook. NIST management officials who supported this effort include: Joan Hash, William C. Barker, Elizabeth Chew, and Matthew Scholl.\nThe authors would like to thank Elizabeth Lennon, Alicia Clay, Elizabeth Chew, Richard Kissel, Carol Schmidt, Matthew Scholl, and Patricia Toth who assisted with reviewing this Handbook and provided comments and suggestions for improvement. Additional drafters of Handbook chapters include:\n\nRon Ross, Tim Grance, and Marianne Swanson, NIST. Nadya Bartol, Joe Nusbaum, Laura Prause, Will Robinson, Karen Kent, and Randy Ewell, BAH,\n\nIn addition, special thanks are due those contractors who helped craft the Handbook, prepare drafts, and review materials:\n\nNadya Bartol of Booz, Allen, Hamiliton (BAH), served as Project Manager for BAH on this project. In addition, many BAH employees contributed to the Handbook, including: Anthony Brown, Linda Duncan, Gina Jamaldinian, Sedar Labarre, Ines Murphy, Steven Peck, Mike Kapetanovic, Michael Rohde, Jacob Tsizis, Aderonke Adeniji, and Marge Spanninger. The authors also gratefully acknowledge and appreciate the many contributions from individuals in the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication. ## Errata\n\nThe following changes have been incorporated into Special Publication 800-100. 1. Chapter 10 Risk Management, Figure 10-1. Risk Management in the System Security Life Cycle diagram has been modified to remove numbers from diagram and to show the steps clearly in the risk management process in the system security life cycle. 2. Chapter 10 Risk Management, Table 10-1. Risk Level Matrix has been modified to correct the math in the diagram. vi\n\n## Table of Contents\n\n| 1. Introduction .................................................................................................... | 1."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective:\n\nrom neighboring jurisdictions or inter-governmental jurisdictions (i.e., state or Federal) need to be integrated into the response, along with the information and communications technologies they use.\nIn a cloud ecosystem, a cloud consumer's ability to comply with any business, regulatory, operational, or security requirements in a cloud computing environment is a direct result of the service and deployment model adopted by the agency, the cloud architecture, and the deployment and management of the resources in the cloud environment. Leveraging NIST's initial cloud computing definition and architecture, the two international standards developers have developed and approved a standardized cloud vocabulary [ISO/IEC 17788 | Recommendation ITU-T Y.3500], and a cloud architecture [ISO/IEC 17789 | Recommendation ITU-T Y.3502]. These standards create a strong foundation for the majority of the current cloud standards development, such as Application Security Validation [ISO/IEC 27034-4], Electronic Discovery [ISO/IEC 27050], Service Level Agreement Framework - Part 4: Security and Privacy [ISO/IEC 19086-4], Guidelines for security of supply chain security-cloud services [ISO/IEC CD 27036-4], and Code of practice for information security controls for cloud services [ISO/IEC FDIS 27017] to list a few of them. Recently approved is a Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors [ISO/IEC 27018:2014]. Other architectural efforts come from the OpenStack Foundation. OpenStack is an open source set of software tools for building and managing cloud computing platforms for public and private clouds. The Institute of Electrical and Electronics Engineers (IEEE) has three projects underway addressing intercloud communications, cloud portability and interoperability profiles, and adaptive management of cloud computing environments."}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Framework Version 1.1 Manufacturing Profile provide? (Part 4)"}, {"role": "assistant", "content": "updates include managing cybersecurity within the supply chain, self-assessing cybersecurity risk, vulnerability disclosure, system integrity, and more comprehensive controls for identity management.\nAdditional changes include updating language to change references from 'security levels' to 'impact levels.'\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. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Executive Summary\n\nThis document provides the Cybersecurity Framework implementation details developed for the manufacturing environment. The 'Manufacturing Profile' of the Cybersecurity Framework can be used as a roadmap for reducing cybersecurity risk for manufacturers that is aligned with manufacturing sector goals and industry best practices. The Profile gives manufacturers:\n\n- A method to identify opportunities for improving the current cybersecurity posture of the manufacturing system\n- An evaluation of their ability to operate the control environment at their acceptable risk level\n- A standardized approach to preparing the cybersecurity plan for ongoing assurance of the manufacturing system's security\n\nThe Profile is built around the primary functional areas of the Cybersecurity Framework which enumerate the most basic functions of cybersecurity activities."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide for Cybersecurity Event Recovery:\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| Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi |\n|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction .........................................................................................................................1 | 1. Introduction .........................................................................................................................1 | 1."}], "metadata": {"source": "Guide for Cybersecurity Event Recovery", "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 Platform Firmware Resiliency Guidelines:\n\n1 | | | 1.1 | Purpose ..........................................................................................................................1 | | | 1.2 | Audience........................................................................................................................1 | | | 1.3 | Applicability and Scope.................................................................................................2 | | | 1.4 | Document Structure.......................................................................................................2 | | 2 | Platform Architecture .........................................................................................................."}], "metadata": {"source": "Platform Firmware Resiliency Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Information System Security Best Practices for UOCAVA-Supporting Systems:\n\nEvery server has at least one way to manage it, and often has at least a few. Some servers are managed directly on the server themselves, using keyboards and monitors attached directly to the servers.\nMore and more, however, servers are managed by workstations (often regular PCs) that access them through local networks and/or the Internet. In the latter case, management access control for the server also means access control for any workstation that can manage the server through its remote interface. Thus, the scope of access control is often much wider than just that of the server itself. It is important to recognize that the management of any particular computer can be done in many ways, not just one."}], "metadata": {"source": "Information System Security Best Practices for UOCAVA-Supporting 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 Access Control?"}, {"role": "assistant", "content": "According to Usability and Security Considerations for Public Safety Mobile Authentication:\n\n| .........................................................................................................\n2 |\n| 2 | Usability of Authentication for Public Safety.......................................................3 | Usability of Authentication for Public Safety.......................................................3 |\n| 2.1 | Why Usability Matters for Public Safety .......................................................... | 3 |\n| 2.2 | Usability Research Methodology | .................................................................... 3 |\n| 2.3 | Qualitative Data from Public Safety SMEs......................................................"}], "metadata": {"source": "Usability and Security Considerations for Public Safety Mobile Authentication", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.8 (NIST 3.2.8)?"}, {"role": "assistant", "content": "According to Research Report_ User Perceptions of Smart Home Privacy and Security:\n\n3.2.8 | Device Hacking | 17 |\n| | 3. 3.2.8 Device Hacking\n\nWithin the security context, participants mentioned that they were concerned about their devices being hacked by unauthorized or malicious actors, as expressed by one participant who worried that hackers would be able to 'shut o GLYPH<11> , or dismantle, or mess with the system that I have in place' (P37\\_A) ."}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "cmmc_level": "all", "nist_control": "3.2.8", "cmmc_practice_id": "AT.L2-3.2.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\nices, including tasks to perform all required security functions (e.g., SBOM generation, vulnerability scanning, code building, code signing, introduction of new testing tools, conducting audit etc.).\nSpecifically, in some instances, members of the security team may be responsible for designing, building, and maintaining Policy as Code and the associated pipeline. - Infrastructure team - Members of this team create, maintain, and upgrade the infrastructure. - QA team - Members of this team develop integration test cases. - Deployment team/release team - Members of this team create pipelines and packages for various environments (UAT/PreProd/Prod) and perform the configuration and provisioning appropriate for these environments."}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Secure Web Services:\n\nfor setting the standards for authentication, authorization, encryption, and nonrepudiation. The provider communicates its requirements through the extensibility of WSDL, a discovery service, or both.\nSome requirements may be negotiable, allowing requesters and providers to dynamically determine how to proceed, but at this time WSDL and discovery services do not provide a standard way for negotiating such requirements. Standards are under development to address this shortcoming."}], "metadata": {"source": "Guide to Secure Web Services", "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 Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\n.....................21 |\n| 2.3.2. Risk Avoidance ............................................................................................................................22 |\n| 2.3.3.\nRisk Transfer................................................................................................................................22 |\n| 2.3.4. Risk Mitigation.............................................................................................................................23 |\n| 2.3.5. Relationship of Risk Response to Risk Strategy ..........................................................................26 |\n| 2.3.6. Implicit Acceptance.....................................................................................................................28 |\n| 2.3.7. Responding to Positive Risk Scenarios ........................................................................................30 |\n| 2.4.1. Risk Response Cost......................................................................................................................31 |\n| 2.4.2. Risk Response Description ..........................................................................................................32 |\n| 2.4.4. Status...........................................................................................................................................34 |\n| Conclusion ...................................................................................................................................36 |\n| 3. |\n| Appendix B. Change Log...................................................................................................................41 |"}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk 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 is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Application Container Security Guide:\n\n3.3.2 不正アクセス | ... 3.3.2 不正アクセス\n\n多くの場合、オーケストレータには、組織内ですでに使用されている一般的なディレクトリとは別の、独自の認証デ ィレクトリサービスが含まれている。これらのシステムは厳密に管理されていないため、オーケストレータ内のより 弱いアカウント管理の慣行と、 「孤立した」アカウントの原因となる可能性がある。これらのアカウントの多くは、 オーケストレータ内で高い特権を与えられているので、これらのアカウントの侵害が、システム全体の侵害につなが る可能性がある。\n\nコンテナは通常、オーケストレーションツールによって管理されるホスト固有ではないデータストレージボリューム を使用する。なぜなら、コンテナはクラスタ内の任意のノードで実行できるため、コンテナ内のアプリが要求するデ ータは、コンテナが実行されているホストに関係なく、コンテナで使用できる必要があるからである。同時に、多く の組織では、不正アクセスを防ぐために、保存時に暗号化する必要があるデータを管理している。\n\n## 3."}], "metadata": {"source": "Application Container Security Guide", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management:\n\n## 3.2.2.2 Reduce Insider Threat of Unauthorized Device Sub-Capability and Defect Check HWAM-L02\n\n| Sub-Capability Name | Sub-Capability Purpose |\n|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Reduce insider threat of unauthorized device | Require multiple persons to authorize adding a device to the authorization boundary (i.e., apply the principle of separation of duties) to limit the ability of a single careless or malicious insider to authorize devices. Note 1: The organization might choose to use access restrictions to enforce the separation of duties. If so, that would be assessed under the PRIV capability. What is assessed here is that the separation of duties occurs. Note 2: See HWAM-L11 for authorization boundary."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to LTE Security provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-187\n\n## Guide to LTE Security\n\nJeffrey Cichonski Joshua M . Franklin Michael Bartock\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-187\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-187\n\n## Guide to LTE Security\n\nJeffrey Cichonski Joshua M. Franklin Applied Cybersecurity Division Information Technology Laboratory\n\nMichael Bartock Computer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-187\n\nDecember 2017\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## 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": "Guide to LTE Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT):\n\n-  Restricting logical access to the network and network activity. This may include using unidirectional gateways, a demilitarized zone network architecture with firewalls to prevent network traffic from passing directly between the corporate and IoT networks, and having separate authentication mechanisms and credentials for users of the corporate and IoT networks. An IoT system should use a network topology that has multiple layers, with each layer's security considered separately, so that all communication occurs with as much security and reliability as afforded by the technology. -  Restricting physical access to IoT network and components. Unauthorized physical access to components could cause serious disruption of an IoT system's functionality. A combination of physical access controls should be used, such as locks, card readers, and/or guards. -  Protecting individual IoT components from exploitation. This includes deploying security patches as expeditiously as possible, after testing them under field conditions; disabling all unused ports and services and assuring that they remain disabled; restricting IoT user privileges to only those that are required for each person's role; tracking and monitoring audit trails; preventing RF attacks and restricting physical access; and using security controls such as antivirus software and file integrity checking software where technically feasible to prevent, deter, detect, and mitigate malware. -  Preventing unauthorized modification of data. This includes data that is in transit (at least across the network boundaries) and at rest. Methods such as encryption and digital signatures can be used to preserve the integrity of data. -  Detecting security events and incidents. Detecting security events, which have not yet escalated into incidents, can help defenders break the attack chain before attackers attain their objectives."}], "metadata": {"source": "Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Security Property Verification by Transition Model:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "Security Property Verification by Transition Model", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Standard Security Label for GOSIP_ an Invitational Workshop:\n\n- open system A set of one or more computers, the associated software, peripherals, terminals, human operators, physical processes, information transfer means, etc., that forms an autonomous whole capable of performing information processing and/or information transfer which complies with the requirements of OSI standards in its communication with other open systems. [3]\n\n- A. Yes, but more work is needed. The Electronic Systems Division of the U.S. Air Force plans to fund a feasibility study of the Multipolicy Machine via a Small Business Innovation Research (SBIR) Phase I grant to Data Security Inc. Starting in July 1991, we will explore these and other issues\n- Q. Several national and international agencies (ECMA and ISO, for example) are working on sensitivity label standards to make information interchange easier between MLS systems. Can the Multipolicy Machine incorporate these evolving standards? - A. Yes. The Multipolicy Machine fits very nicely with the European standards. 4. Qe Can we design a Multipolicy Machine which is simple to manufacture, evaluate, and accredit? Can commercial offthe-shelf components be used? - A. I hope the answer to both questions is yes, but need more time to engineer the technology. - Q. How much more complicated will it be to evaluate multiple instead of single policy machines? - A. Although initially more difficult, it will eventually be easier to evaluate multiple policy machines than single policy machines because the policy will be separate from the mechanisms. Now, policy and mechanisms are integrated and must be evaluated together. When rule-based or other machines which separate policy from mechanism are accepted, it will be sufficient for the vendor to prove to the evaluators that their mechanisms implement any of a set of security policies. Proving that the particular policy of a particular installation is valid and supported by the mechanism is left to the certification and accreditation process\n- Q."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "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 Bluetooth Security:\n\n| NIST SP 800-53 Control Number and Name | Recommendation Numbers from Table 4-2 | |------------------------------------------------------------------|-------------------------------------------| | AT-2, Security Awareness Training | 2, 5 | | CA-2, Security Assessments | 3 | | CM-6, Configuration Settings | 7 | | CM-7, Least Functionality | 17, 18, 27 | | CM-8, Information System Component Inventory | 6 | | IA-2, Identification and Authentication (Organizational Users) | 25, 26 | | IA-3, Device Identification and Authentication | 9, 11, 12, 13, 14, 16, 21, 28, 29, 30, 31 | | IR-4, Incident Handling | 31 | | RA-3, Risk Assessment | 4, 35 | | SC-1, System and Communications Protection Policy and Procedures | 1 | | SC-12, Cryptographic Key Establishment and Management | 10, 15, 16, 23, 25 | | SC-40, Wireless Link Protection | 8, 28 | | SC-8, Transmission Confidentiality and Integrity | 13, 14, 16, 19, 20, 22, 29 | | SI-2, Flaw Remediation | 33 | | SI-3, Malicious Code Protection | 32 | | SI-5, Security Alerts, Advisories, and Directives | 36 |"}], "metadata": {"source": "Guide to Bluetooth Security", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\n| 3.2 SWAM Sub-Capabilities and Defect Check Tables and Templates......................................27 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 3.2.1 Foundational Sub-Capabilities and Corresponding Defect Checks...............................28 | | 3.2.2 Data Quality Sub-Capabilities and Corresponding Defect Checks ...............................37 | | 3.2.3 Local Sub-Capabilities and Corresponding Defect Checks ...........................................45 | | 3.2.4 Security Impact of Each Sub-Capability on an Attack Step Model ................................74 | | 3.3 SWAM Control (Item) Security Assessment Plan Narrative Tables and Templates.............82 | | 3.3.1 Outline Followed for Each Control Item........................................................................83 | | 3.3.2 Outline Organized by Baselines......................................................................................83 | | 3.3.3 Low Baseline Security Control Item Narratives .............................................................85 | | 3.3.4 Moderate Baseline Security Control Item Narratives ..................................................115 | | 3.3.5 High Baseline Security Control Item Narratives..........................................................148 | | 3.4 Control Allocation Tables (CATs)......................................................................................165 | | 3.4.1 Low Baseline Control Allocation Table........................................................................166 | | 3.4.2 Moderate Baseline Control Allocation Table...............................................................168 | | 3.4.3 High Baseline Control Allocation Table.......................................................................169 | | Appendix A."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to System and Network Security Acronyms and Abbreviations:\n\nds of electromagnetic radiation to personnel |\n| HF | high frequency |\n| HFS | Hierarchical File System |\n| HHS | U.S.\nDepartment of Health and Human Services |\n| HINFO | host information |\n| HIP | Host Identity Protocol |\n| HIPAA | Health Insurance Portability and Accountability Act |\n| HIPERLAN | high-performance radio local area network |\n| HKLM | HKEY_Local_Machine |\n| HL7 | Health Level Seven |\n| HMAC | keyed-hash message authentication code |\n| HMI | human-machine interface |\n| HPA | host protected area |\n| HPFS | High-Performance File System |\n| HR | human resources |\n| HSARPA | Homeland Security Advanced Research Projects Agency |\n| HSPD | Homeland Security Presidential Directive |\n| HTCIA | High Technology Crime Investigation Association |\n| HTCP | Hyper Text Caching Protocol |\n| HTML | Hypertext Markup Language |\n| HTTP | Hypertext Transfer Protocol |\n| HTTPS | Secure Hypertext Transfer Protocol |\n| Hz | hertz |"}], "metadata": {"source": "System and Network Security Acronyms and Abbreviations", "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 2 require for Planning?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8.\nContingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12. Media Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to A Review of U.S. and European Security Evaluation Criteria:\n\n| ABSTRACT | ABSTRACT | | | |\n|------------|------------------------------------------------------------------------------------------------------------------|----------------|----|----|\n| KEY | WORDS | | 1 | 1 |\n| 1 . 0 | INTRODUCTION | | | |\n| 2 . 0 | TRUSTED SYSTEM EVALUATION CRITERIA | COMPUTER | | |\n| 3 . 0 | TRUSTED INTERPRETATION | NETWORK | | |\n| 4 . 0 | TRUSTED MANAGEMENT SYSTEM INTERPRETATION ... | DATABASE | | |\n| 5.0 | IT SECURITY CRITERIA - CRITERIA FOR THE EVALUATION OF THE TRUSTWORTHINESS OF INFORMATION TECHNOLOGY (IT) SYSTEMS | | | |\n| 6 . 0 | DRAFT TECHNOLOGY SECURITY EVALUATION CRITERIA | INFORMATION | | |\n| 7.0 | ANALYSIS OF SECURITY CRITERIA SETS ... | AND COMPARISON | | |\n| 7.1 | U.S. EVALUATION CRITERIA - ORANGE BOOK, RED BOOK, | SECURITY TDI | | |\n| 7.2 | U.S. SECURITY EVALUATION CRITERIA | vs."}], "metadata": {"source": "A Review of U.S. and European Security Evaluation Criteria", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic:\n\nThe Mayo Clinic's vendor onboarding process is a critical tool for cyber supply chain risk management. Suppliers are contractually obligated to comply with the Mayo Clinic's information security schedule or demonstrate mitigating controls to account for particular requirements. These requirements include cybersecurity, physical security, and ethical behavior requirements particular to their product or service category group. Many of these requirements are publicly available for potential suppliers to review before engaging the Mayo Clinic iii, iv .\n\nThe key focus of the Mayo Clinic's cybersecurity and supply chain incident response plans is the continuation of patient care. A dedicated business continuity team within the SCM manages supply chain resiliency events, which are often first identified by other hospitals and health networks that share the supplier. For instance, when the Illinois Environmental Protection Agency shut down the medical supply sterilization company Sterigenics v in February 2019, the Mayo Clinic's business continuity team proactively engaged vendors reliant on Sterigenics to identify alternative sourcing. The business continuity team stores safety reserves of critical supplies to mitigate the impact of supply chain disruptions. While most Mayo Clinic facilities leverage high-efficiency 'just-in-time' operations and supply delivery, these reserves may be deployed to any facility in the network."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic", "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 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 does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Computer Security Division 2004 Annual Report:\n\nThe Division has had many other accomplishments this past year, including advancing development of our cryptographic standards toolkit, further e-authentication work, expansion of our Cryptographic Module Validation Program, development of an IT product security configuration checklist program and more work with digital forensics tools and methods. We have begun new work, as well as continuing previous work, on several key Internet security protocols - IPSec, BGP and DNSSEC. We have also provided technical expertise to several U.S. government groups on the security implications of spam e-mail and phishing attacks.\n\nTo keep pace with the rate of change in emerging technologies we conduct a large of amount of research into existing and emerging technologies. Some of the many topics we research include smart card infrastructure and security, wireless and mobile device security, voice over IP security issues, digital forensics tools and methods, access control and authorization management, Internet Protocol security, intrusion detection systems, quantum information system security and quantum cryptography and vulnerability analyses. Our research helps fulfill specific needs by the Federal government that would not be easily or reliably filled otherwise.\n\nMany different types of people use ICAT for a variety of purposes. System administrators and computer security officers use ICAT to identify the known vulnerabilities (and patch information) associated with the software on critical systems. Law enforcement can use ICAT in forensics activities to determine the set of possible vulnerabilities that a hacker might have used to penetrate a system. Computer security researchers use ICAT to identify sets of vulnerabilities that have particular characteristics of interest. Auditors can use ICAT to check to see if particular vulnerabilities have been patched in audited systems."}], "metadata": {"source": "Computer Security Division 2004 Annual Report", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Computer Security Log Management:\n\n| 5.3 | Respond to Identified Events................................................................................. | 5-8 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------------|\n| 5.4 | Manage Long-Term Log Data Storage .................................................................. | 5-9 |\n| 5.5 | Provide Other Operational Support...................................................................... | 5-10 |\n| 5.6 | Perform Testing and Validation ........................................................................... | 5-10 |\n| 5.7 | Summary............................................................................................................."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nTemoshok D, Abruzzi C, Choong YY, Fenton JL, Galluzzo R, LaSalle C, Lefkovitz N,\nRegenscheid A, Vachino M (2025) Digital Identity Guidelines: Identity Proofing and\nEnrollment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST\nSpecial Publication (SP) NIST SP 800-63A-4. https://doi.org/10.6028/NIST.SP.800-63A-4"}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8425/a/final including related content, potential updates, and document history. - Machine-readable asset identification support. Consumer-grade routers serve as a central connection point for networks. Many types of devices will gain access to the local network and usually the internet. Consumer grade routers can be more proactive in managing the cybersecurity of the network when machine-readable asset identifiers are available. While home users could utilize machine-readable asset identification, it is more likely to be useful to small businesses or for routers leased from internet service providers (ISPs). Identification can also go beyond simple inventorying to include device type and firmware version, be extended by concepts like device intent signaling (e.g., the ' manufacturer usage description ' [MUD]) or be used more directly for the management of router devices ' firmware updates. Machine-readable asset identifiers must be developed and used in ways that are privacy preserving. - Interface and functionality minimization for consumer-grade router devices. ' Secureby-design ' principles [SecureByDesign] applied to consumer-grade routers should guide manufacturers to minimize the number of interfaces, both logical and physical and general functionality provided by the router device. The primary functionality of the home router is to provide access to the Internet for devices within the home. Extraneous functions should not be included in this component. For example, configuration may be better managed by another product component (e.g., mobile application). This is not to suggest a product composed of only a router device is necessarily less secure than those that can offload functions to other components.. - Robust network onboarding support from consumer-grade router products."}], "metadata": {"source": "Recommended Cybersecurity Requirements for Consumer-Grade Router Products", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for API Protection for Cloud-Native Systems:\n\nards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology.\nITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Guidelines for API Protection for Cloud-Native Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cloud Computing Synopsis and Recommendations:\n\n| Hardware Support for Trust........................................................................\n| 8-9 |\n| | 8.5.7 | Key Management....................................................................................... | 8-9 |\n| 9. General Recommendations........................................................................................... | 9. General Recommendations........................................................................................... | 9. General Recommendations..........................................................................................."}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "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 Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards provide? (Part 5)"}, {"role": "assistant", "content": "------|\n| Identify | ID. AM | Asset Management |\n| Identify | ID. BE | Business Environment |\n| Identify | ID.\nGV | Governance |\n| Identify | ID.RA | Risk Assessment |\n| Identify | ID.RM | Risk Management Strategy |\n| Identify | ID.SC | Supply Chain Risk Management |\n| Protect | PR.AC | Identity Management and Access Control |\n| Protect | PR.AT | Awareness and Training |\n| Protect | PR.DS | Data Security |\n| Protect | PR.IP | Information Protection and Procedures |\n| Protect | PR.MA | Maintenance |\n| Protect | PR.PT | Protective Technology |\n| Detect | DE.AE | Anomalies and Events |\n| Detect | DE.CM | Security Continuous Monitoring |\n| Detect | DE.DP | Detection Processes |\n| Respond | RS.RP | Response Planning |\n| Respond | RS.CO | Communications |\n| Respond | RS.AN | Analysis |\n| Respond | RS.MI | Mitigation |\n| Respond | RS.IM | Improvements |\n| Recover | RC.RP | Recovery Planning |\n| Recover | RC.IM | Improvements |\n| Recover | RC.CO | Communications |\n\nThese informative references provide practical suggestions for how organizations can achieve the desired outcome of each Subcategory."}], "metadata": {"source": "Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Proxy Validation and Verification for Critical AI Systems_ A Proxy Design Process:\n\nAdditional information about this publication is available at https://csrc.nist.gov/publications/cswp, including related content, potential updates, and document history.\n\n1. Chemical: Basic chemicals, specialty chemicals, agricultural chemicals, and consumer products\n2. Commercial facilities: Entertainment/media, gaming, lodging, outdoor events, public assembly, real estate, retail, and sports leagues\n3. Communications: Providers of voice services using interconnected terrestrial, satellite, and wireless transmission systems\n4. Critical manufacturing: Metals; machinery; electrical equipment, appliances, and components; and transportation equipment\n5. Dams: Critical water retention and control services\n6. Defense industrial base: Research, development, production, delivery, and maintenance of military weapons systems, subsystems, and components or parts to meet U.S. military requirements\n7. Emergency services: Highly skilled and trained personnel and physical and cyber resources that provide prevention, preparedness, response, and recovery services during day-to-day operations and incident response\n8. Energy: Electricity, oil, and natural gas\n9. Financial services: Depository institutions, providers of investment products, insurance companies, other credit and financial organizations, and providers of critical financial utilities and services that support these functions"}], "metadata": {"source": "Proxy Validation and Verification for Critical AI Systems_ A Proxy Design Process", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Threat Analysis on UOCAVA Voting Systems provide? (Part 5)"}, {"role": "assistant", "content": "| 4 | | 2.1.1 | 2.1.1 | FWAB......................................................................................................................................4 | | | 2.1.2 | 2.1.2 | Electronic Transmission Service.............................................................................................4 | | | 2.1.3 | 2.1.3 | Voting over the Internet...........................................................................................................5 | | | 2.1.4 | 2.1.4 | SERVE.....................................................................................................................................5 | | | 2.1.5 | 2.1.5 | Interim Voting Assistance System ...........................................................................................6 | | | 2.2 | 2.2 | CURRENT UOCAVAVOTING PROCESS..........................................................................."}], "metadata": {"source": "A Threat Analysis on UOCAVA Voting Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio:\n\n| Action | Description |\n|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| De-duplicate and combine identical or similar risks | An external attacker deploys a remote access tool and uses it to exfiltrate the plans for the company's upcoming merger. External threat actors steal information about marketing plans through malicious code deployed in the sales department. Malicious parties plant a web shell in an external site that enables them to access documents stored in the Legal Affairs shared document folder, resulting in the loss of critical corporate information. |\n| Reprioritize according to risk appetite, tolerance, and sensibilities | Since priorities have been established at organization and system levels, it may be necessary to review their collective priority and recommend adjustments to a higher or lower priority."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "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 National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\nThis National Institute of Standards and Technology Interagency Report (NISTIR) presents the National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook . The Handbook provides NASA's overall approach to automated information systems security including: program goals and objectives, assignment of responsibilities, risk assessment, foreign national access, contingency planning and disaster recovery, awareness training, procurement, certification, planning, and special considerations for microcomputers. | Paraaraoh | | | Pace |\n|-------------|-------------------------------------------------------|-------------------------------------------------------|--------|\n| | c. | Personnel Screening | 3-6 |\n| | d. | Access Protection and Accountability | 3-6 |\n| | e. | Compliance Assurance | 3-6 |\n| | f | Contingency and Disaster Recovery Plans | 3-7 |\n| | g- | Approval of Methodologies | 3-7 |\n| 303 | Risk | Assessment Process | 3-7 |\n| 304 | Protective Measures to Prevent Misuse and Abuse | Protective Measures to Prevent Misuse and Abuse | 3-10 |\n| 305 | Certification | Process | 3-10 |\n| | a. | New or Modified Applications | 3-11 |\n| | b."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "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 Guide to Secure Web Services:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | |---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | Introduction | | ......................................................................................................................1-1 | | | 1.1 | Authority...................................................................................................................1-1 | Authority...................................................................................................................1-1 | | | 1.2 | Purpose and Scope .................................................................................................1-1 | Purpose and Scope .................................................................................................1-1 | | | 1.3 | Audience..................................................................................................................1-1 | Audience..................................................................................................................1-1 | | | 1.4 | Document Structure.................................................................................................1-2 | Document Structure.................................................................................................1-2 | | | 2."}], "metadata": {"source": "Guide to Secure Web Services", "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 Directions in Security Metrics Research:\n\nCryptographic mechanisms are an area where research results exist and bounds on the effort required to breach components could be determined, under specific assumptions. Extending this type of analysis to trust mechanisms is a more challenging problem, but one with significant benefits, if achieved. Components that rely on certain surety mechanisms, such as authentication modules designed for passwords or biometric modules for fingerprints, lend themselves to certain types of strength analysis (e.g., password space size [Lee08]), and results already exist that could be applied. Finally, techniques for strength analysis might also be drawn from physical security, such as metrics used by industry to evaluate safe and vault security and identify weaknesses leading to failure [Bla04]."}], "metadata": {"source": "Directions in Security Metrics Research", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 1 – General:\n\n3.3.2 Cost of Key Revocation and Replacement... 3.3.2 | Private Authentication Keys... 3.3.2 Cost of Key Revocation and Replacement\n\nIn some cases, the costs associated with changing keys are painfully high."}], "metadata": {"source": "Recommendation for Key Management_ Part 1 – General", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\n| APPENDIX A: GLOSSARY OF TERMS............................................................................. A- | 1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|\n| APPENDIX B: REFERENCES...............................................................................................B- | 1 |\n| APPENDIX C: MANAGEMENT AND SUPPORT INFORMATION AND INFORMATION SYSTEMS IMPACT LEVELS................................................................ | 1 |\n| C.1 Recommended Provisional Impact Levels for Management and Support Information Types..................................................................................................................... | 2 7 |\n| C.2 Rationale and Factors for Services Delivery Support Information ..................................."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Key Derivation Using Pseudorandom Functions:\n\nIn keeping with the usual terminology, the output of a key-derivation function is called the derived keying material and may subsequently be segmented into multiple keys. Any disjoint segments of the derived keying material (with the required lengths) can be used as cryptographic keys for the intended algorithms. Two different key-establishment scenarios may use the KDF: one in which multiple parties share the same key-derivation key and are able to separately derive the same keying material, and the other in which one entity derives keying material using a keyderivation key known only to itself and distributes the derived keying material to other entities. When multiple parties share the same key-derivation key, the cryptographic application employing a KDF must define the way to convert (i.e., parse) the keying material into different keys. For example, when 256 bits of keying material are derived, the application may specify that the first 128 bits will be used as a key for a message authentication code and that the second 128 bits will be used as an encryption key for a given encryption algorithm. In the case where a single party derives the keying material, a re-derivation can produce the same keys (when required). - [1] Barker EB, Roginsky AL, Davis R (2020) Recommendation for Cryptographic Key Generation. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-133, Rev. 2. https://doi.org/10.6028/NIST.SP.800-133r2\n- [2] Barker EB, Chen L, Roginsky AL, Vassilev A, Davis R (2018) Recommendation for PairWise Key-Establishment Schemes Using Discrete Logarithm Cryptography. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-56A, Rev. 3. https://doi.org/10.6028/NIST.SP.800-56Ar3\n- [3] Barker EB, Chen L, Roginsky AL, Vassilev A, Davis R, Simon S (2019) Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography."}], "metadata": {"source": "Recommendation for Key Derivation Using Pseudorandom Functions", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\nNIST Special Publication (SP) 800-157 contains technical guidelines for the implementation of standards-based, secure, reliable, interoperable Public Key Infrastructure (PKI)-based identity credentials that are issued for mobile devices by federal departments and agencies to individuals who possess and prove control over a valid Personal Identity Verification (PIV) Card. This document, SP 800-166, contains the requirements and test assertions for testing the Derived PIV Application and associated Derived PIV data objects implemented on removable hardware tokens and within mobile devices. The tests reflect the design goals of interoperability and interface functions.\n\nauthentication; derived PIV application; derived PIV application data model; derived PIV credential; derived test requirements (DTR); FIPS 201; implementation under test (IUT); mobile devices; Personal Identity Verification (PIV); test assertions; token command interface.\n\nThis document is targeted at vendors of Derived PIV Applications, issuers of Derived PIV Credentials, and entities that will conduct tests on these applications and credentials. Readers are assumed to have a working knowledge of SP 800-157, FIPS 201 and other PIV guidelines, and applicable technologies. This document is intended to:"}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Application Container Security Guide:\n\n3.3.5 オーケストレータノードの信頼 ... 3.3.5 オーケストレータノードの信頼\n\n環境内のノード間の信頼の維持には特別な注意が必要である。オーケストレータは最も中心となるノードである。脆 弱なオーケストレータの設定は、オーケストレータと他のすべてのコンテナ技術コンポーネントをリスクにさらす可 能性がある。考えられる結果の例としては、以下のようなものがある。\n\n- 不正なホストがクラスタに参加し、コンテナを実行\n- 一つのクラスタのホストの侵害が、クラスタ全体に侵害をもたらす。例えば、同じ認証用の鍵ペアが、すべ てのノードで共有されている場合など。\n- オーケストレータと DevOps 担当者、管理者、およびホスト間の通信が暗号化されず、認証もされない。\n\n## 3."}], "metadata": {"source": "Application Container Security Guide", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC provide? (Part 5)"}, {"role": "assistant", "content": "9.2 | 9.2 | OPERATIONAL CONSIDERATIONS ..............................................................................................................23 | | | 10 CONFORMANCE...........................................................................................................................................24 | 10 CONFORMANCE...........................................................................................................................................24 | 10 CONFORMANCE...........................................................................................................................................24 | | | APPENDIX A: IMPORTANCE OF THE UNIQUENESS REQUIREMENTON IVS.....................................25 | APPENDIX A: IMPORTANCE OF THE UNIQUENESS REQUIREMENTON IVS.....................................25 | APPENDIX A: IMPORTANCE OF THE UNIQUENESS REQUIREMENTON IVS.....................................25 | | | APPENDIX B: AUTHENTICATION ASSURANCE...........................................................................................26 | APPENDIX B: AUTHENTICATION ASSURANCE...........................................................................................26 | APPENDIX B: AUTHENTICATION ASSURANCE...........................................................................................26 | | | APPENDIX C: REQUIREMENTS AND GUIDELINES FOR USING SHORT TAGS....................................28 | APPENDIX C: REQUIREMENTS AND GUIDELINES FOR USING SHORT TAGS....................................28 | APPENDIX C: REQUIREMENTS AND GUIDELINES FOR USING SHORT TAGS....................................28 | | | APPENDIX D: PROTECTION AGAINST REPLAY OF MESSAGES.............................................................30 | APPENDIX D: PROTECTION AGAINST REPLAY OF MESSAGES.............................................................30 | APPENDIX D: PROTECTION AGAINST REPLAY OF MESSAGES.............................................................30 | | | APPENDIX E: BIBLIOGRAPHY..........................................................................................................................31 | APPENDIX E: BIBLIOGRAPHY..........................................................................................................................31 | APPENDIX E: BIBLIOGRAPHY..........................................................................................................................31 | | ## NIST Special Publication 800-38D | List of Figures | List of Figures | |------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | Figure 1: GHASH H ( X 1 || X 2 || ..."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Digital Identity Guidelines_ Authentication and Authenticator Management provide? (Part 4)"}, {"role": "assistant", "content": "at https://csrc.nist.gov/pubs/\nsp/800/63/B/4/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA).\nNIST SP 800-63B-4\nJuly 2025\n\nAbstract\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nThis guideline focuses on the authentication of subjects who interact with government\ninformation systems over networks to establish that a given claimant is a subscriber\nwho has been previously authenticated. The result of the authentication process may\nbe used locally by the system performing the authentication or asserted elsewhere in a\nfederated identity system. This document defines technical requirements for each of the\nthree authentication assurance levels. The guidelines are not intended to constrain the\ndevelopment or use of standards outside of this purpose. This publication supersedes\nNIST Special Publication (SP) 800-63B. Keywords\n\nauthentication; authentication assurance; credential service provider; digital\nauthentication; passwords. Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cell Phone Forensic Tools_ an Overview and Analysis Update:\n\nFigure 1 gives an overview of the hardware characteristics of basic, advanced, and high-end cell phones for display quality, processing and storage capacity, memory and I/O expansion, built-in communications, and video and image capture. The bottom of the diagram shows the range of cellular voice and data advances from kilobit analog networks, still in use today, to megabit 3 rd generation digital networks in the planning and early deployment stages. The diagram attempts to illustrate that more capable phones can capture and retain not only more information, but also more varied information, through a wider variety of sources, including removable memory modules, other wireless interfaces, and built-in hardware. Note that hardware components can and do vary from those assignments made in the diagram and, over time, technology once considered high end or advanced eventually appears in what would then be considered a basic phone."}], "metadata": {"source": "Cell Phone Forensic Tools_ an Overview and Analysis Update", "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 Access Control?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\n| CHAPTER ONE INTRODUCTION.......................................................................................1 | CHAPTER ONE INTRODUCTION.......................................................................................1 | | |----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| | 1.1 | BACKGROUND ......................................................................................................2 | | | 1.2 | RELATIONSHIP TO OTHER PUBLICATIONS ..................................................................2 | | | 1.3 | PURPOSE.............................................................................................................3 | | | 1.4 | TARGET AUDIENCE | ................................................................................................3 | | 1.5 | ORGANIZATION OF THIS SPECIAL PUBLICATION | ..........................................................4 | | CHAPTER TWO THE FUNDAMENTALS ..............................................................................5 | CHAPTER TWO THE FUNDAMENTALS ..............................................................................5 | | | 2.1 | ORGANIZATION-WIDE VIEW OF ISCM.........................................................................6 | | | 2.2 | ONGOING SYSTEM AUTHORIZATIONS .....................................................................10 | | | 2.3 | ROLE OF AUTOMATION IN ISCM..............................................................................12 | | | 2.4 | ISCM ROLES AND RESPONSIBILITIES ......................................................................13 | | | CHAPTER THREE THE PROCESS...................................................................................16 | CHAPTER THREE THE PROCESS...................................................................................16 | | | 3.1 | DEFINE ISCM STRATEGY.......................................................................................17 | | | 3.2 | ESTABLISH AN ISCM PROGRAM..............................................................................24 | | | 3.3 | IMPLEMENT AN ISCM PROGRAM.............................................................................30 | | | 3.4 | ANALYZE DATA AND REPORT FINDINGS ..................................................................31 | | | 3.5 | RESPOND TO FINDINGS ........................................................................................33 | | | 3.6 | REVIEW AND UPDATE THE MONITORING PROGRAM AND STRATEGY ............................34 | | | APPENDIX A REFERENCES ...........................................................................................A-1 | APPENDIX A REFERENCES ...........................................................................................A-1 | | | APPENDIX B GLOSSARY.............................................................................................."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Module-Lattice-Based Key-Encapsulation Mechanism Standard:\n\ntional Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-108r1-upd1, Includes updates as of February 2, 2024. https://doi.org/10.6028/NIST.SP. 800-108r1-upd1.\n- [17] Barker EB, Chen L, Davis R (2020) Recommendation for key-derivation methods in keyestablishment schemes (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-56C Revision 2. https://doi.org/10.6028/NIST.SP.800-56C r2. - [18] Barker EB, Kelsey JM (2015) Recommendation for random number generation using deterministic random bit generators, (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-90A, Rev. 1. https://doi.org/10.6028/NIST.SP. 800-90Ar1. - [19] Sönmez Turan M, Barker EB, Kelsey JM, McKay KA, Baish ML, Boyle M (2018) Recommendation for the entropy sources used for random bit generation, (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-90B. https://doi.org/10.6028/NIST.SP.800-90B. - [20] Barker E, Kelsey J, McKay K, Roginsky A, Turan MS (2024) Recommendation for random bit generator (RBG) constructions, (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-90C 4pd. https://doi.org/10.6028/NIST.SP.80 0-90C.4pd. - [21] Kelsey J, Chang S, Perlner R (2016) SHA-3 Derived Functions: cSHAKE, KMAC, TupleHash and ParallelHash, (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-185 [or as amended]. https://doi.org/10.6028/NIST.SP.800-1 85. - [22] National Institute of Standards and Technology (2016) Submission requirements and evaluation criteria for the post-quantum cryptography standardization process. Available at https://csrc.nist.gov/CSRC/media/Projects/Post-Quantum-Cryptography/documents/call-f or-proposals-final-dec-2016.pdf."}], "metadata": {"source": "Module-Lattice-Based Key-Encapsulation Mechanism Standard", "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 AC.L2-3.1.11 (NIST 3.1.11)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.1.11. 3.1.11."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "nist_control": "3.1.11", "cmmc_practice_id": "AC.L2-3.1.11", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability:\n\nA Proposed Metric for Vulnerability Exploitation Probability\n\nMell P, Spring J (2025) Likely Exploited Vulnerabilities: A Proposed Metric for Vulnerability Exploitation Probability. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 41. https://doi.org/10.6028/NIST.CSWP.41\n\nThis work presents a proposed security metric to determine the likelihood that a vulnerability has been observed to be exploited. Only a small fraction of the tens of thousands of software and hardware vulnerabilities that are published every year will be exploited. Predicting which ones is important for the efficiency and cost effectiveness of enterprise vulnerability remediation efforts. Currently, such remediation efforts rely on the Exploit Prediction Scoring System (EPSS), which has known inaccurate values, and Known Exploited Vulnerability (KEV) lists, which may not be comprehensive. The proposed likelihood metric may augment EPSS remediation (correcting some inaccuracies) and KEV lists (enabling measurements of comprehensiveness). However, collaboration with industry is necessary to provide necessary performance measurements."}], "metadata": {"source": "Likely Exploited Vulnerabilities_ A Proposed Metric for Vulnerability Exploitation Probability", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI):\n\nImplementation of an [HSPD-12] program exposes an organization to specific risks at the mission level of the organization. The PIV Card is used to establish assurance of an identity, and as such, it must be trusted as a basis for granting access to the logical and physical resources of the organization. Similarly, the Derived PIV Credential is also used to establish the assurance of an identity, and must be trusted as a basis for granting access from mobile devices to the remote IT resources of the organization. Any problem with an issued PIV Card or Derived PIV Credential that undermines this assurance could expose an organization to harm. Furthermore, the collection, processing, and dissemination of personal information is required to issue these credentials and thereby increases the threat of this information being used for malicious purposes 14 if not secured. It is the DAO's responsibility to weigh the risks of these and other security and privacy impacts when making the authorization decision. Furthermore, as [HSPD12] is a government-wide mandate based on a standard of interoperability allowing organizations to accept other organizations' credentials, authorization decisions within a single organization\n\nThe evidence that ensures the presence of issuer controls that are derived from FIPS 201-2 requirements and its related documents as well as OMB Memoranda, and verified through appropriate assessments, establishes the capability of the issuer. However, authorization is generally based not merely on the demonstration of capability, but also on the presence of certain organizational characteristics that will provide a high degree of confidence to the Assessor that the demonstrated capabilities will be carried out in a dependable and sustainable manner."}], "metadata": {"source": "Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Computer Security Division 2015 Annual Report:\n\ning group has been working on developing a draft of SP 800-173, Guidance for Applying the Risk Management Framework to Federal-based Information Systems (target release date: spring/summer 2016).\nIn response to the rapidly emerging use of virtualization in enterprise data centers for supporting both in-house mission-critical applications and for providing cloud services, two guidance documents were published: Draft SP 800-125A, Security Recommendations for Hypervisor Deployment, and Draft SP 800-125B, Secure Virtual Network Configuration for Virtual Machine (VM) Protection. In support of the revised FIPS 201, Personal Identity Verification (PIV) of Federal Employees and Contractors, two new PIV-related SP 800-series were released and five SP 800 documents were revised. One of the new publications, SP 800-157, Guidelines for Derived Personal Identity Verification (PIV) Credentials, guides the implementation and deployment of PIV credentials for mobile devices. In addition, the PIV team participated in the Office of Management and Budget (OMB) cybersecurity Sprint effort with a goal to strengthen the cybersecurity of federal networks, systems, and data through multi-factor authentication using the PIV Card. To improve access to new technologies, the group also chaired, edited, and participated in the development of a wide variety of national and international security standards."}], "metadata": {"source": "Computer Security Division 2015 Annual Report", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines on Securing Public Web Servers:\n\n| Introduction ......................................................................................................................1-1 | | | | | 1.1 | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope .................................................................................................1-1 | | | | 1.3 | Audience and Assumptions .....................................................................................1-2 | | | | 1.4 Document | Structure.................................................................................................1-2 | | | 2."}], "metadata": {"source": "Guidelines on Securing Public Web Servers", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\n................................................................. 40\n3.2.4 Define and Analyze Specific Alternatives ..................................................................................\n43\n3.2.5 Develop Recommendations ...................................................................................................... 46"}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Using Business Impact Analysis to Inform Risk Prioritization and Response provide? (Part 3)"}, {"role": "assistant", "content": "RCID iDs\n\nStephen D. Quinn: 0000-0003-1436-684X Nahla Ivy: 0000-0003-4741-422X\n\nMatthew Barrett: 0000-0002-7689-427X\n\nLarry Feldman: 0000-0003-3888-027X\n\nDaniel Topper: 0000-0003-2612-7547\n\nGregory A.\nWitte: 0000-0002-5425-1097\n\n## Contact Information\n\nnistir8286@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8286/d/upd1/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nWhile business impact analysis (BIA) has historically been used to determine availability requirements for business continuity, the process can be extended to provide a broad understanding of the potential impacts of any type of loss on the enterprise mission. The management of enterprise risk requires a comprehensive understanding of mission-essential functions (i.e., what must go right) and the potential risk scenarios that jeopardize those functions (i.e., what might go wrong). The process described in this publication helps leaders determine which assets enable the achievement of mission objectives and evaluate the factors that render assets as critical and sensitive. Based on those factors, enterprise leaders provide risk directives (i.e., risk appetite and tolerance) as input to the BIA. System owners then apply the BIA to developing asset categorization, impact values, and requirements for the protection of critical or sensitive assets."}], "metadata": {"source": "Using Business Impact Analysis to Inform Risk Prioritization and Response", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh:\n\n- An authenticatable runtime identity for services, authenticable credentials for individual users of the service, and encryption of communication between services.\n- A Policy Enforcement Point (PEP) that is separately deployable and controllable from the application. The role of Policy Decision Point (PDP) can be filled by the service mesh's sidecar proxies or an external service.\n- Logs and metrics for monitoring policy enforcement.\n\nThe service mesh's native feature to authenticate end-user credentials attached to the request (e.g., using a Java Web Token [JWT]) is augmented in many offerings to provide the ability to call external authentication and authorization systems on behalf of the application. The capability to deploy these authentication and authorization systems as services in the mesh also provides operational assurances for encryption in transit, identity, a PEP, authentication, and authorization for end-user identity.\n\n- Multiple, loosely coupled microservices communicate through network calls, and these communication links must be protected. In the case of monolithic applications, these communications take place through procedure calls.\n- The entire network and all microservices are untrusted. Therefore, mutual authentication and secure communication channels between microservices through mechanisms such as mutual Transport Layer Security (TLS) (mTLS) are required.\n- The logging data that pertains to each microservice must be consolidated to obtain a security profile in order for forensics, audits, and analytics to assess the overall health of the application."}], "metadata": {"source": "Attribute-based Access Control for Microservices-based Applications using a Service Mesh", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cloud Computing Synopsis and Recommendations:\n\ncollaboration between providers and consumers can help ensure that clouds meet specific security conformance and regulatory requirements, especially for those supporting government agency operations.\n| Technical | Operational | Management |\n|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|\n| Access Control Audit and Accountability Identification and Authentication System and Communication Protection | Awareness and Training Configuration and Management Contingency Planning Incident Response Maintenance Media Protection Physical and Environmental Protection Personnel Security System and Information Integrity | Certification, Accreditation and Security Assessment Planning Risk Assessment System and Services Acquisition |"}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "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 to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n- Harden software, such as enforcing the principles of least privilege and least functionality (e.g., deactivating or uninstalling software services, features, and other components that are not needed). For additional information on hardening assets, especially those considered critical, see the NIST publication Security Measures for 'EO-Critical Software' Use Under Executive Order (EO) 14028 (July 9, 2021). - Acquire software that is likely to have fewer vulnerabilities over time compared to other software. - Work with software development partners that are likely to introduce fewer vulnerabilities into software over time, taking into consideration factors such as how rigorous their secure software development practices are, how quickly they address issues and release patches, how often problems are associated with their patches, and how transparent they are in their security-related communications. - Use managed services instead of software when feasible. 1. Will you be releasing updates for this software to address vulnerabilities? 2. Approximately how many patches, updates, and upgrades do you expect to release each year for this software? On average, how quickly do you expect to address each vulnerability and release a patch? Do you bundle patches together or is each patch separate? How often do you anticipate releasing emergency updates? 3. For how many years are you committed to correcting vulnerabilities in the software? 4. Will you release updates on a regular schedule, as needed, or both? If a schedule will be followed, what is that schedule (weekly, monthly, quarterly, etc.)? 5. Do you have a vulnerability disclosure and incident response program for your software? How transparent are you in your security-related communications to your customers? 6. When a vulnerability in your software becomes public but a patch, update, or upgrade is not available, how do you recommend that customers protect their computing assets running your software?"}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N:\n\nAn XACML request is a collection of attribute name, value pairs for the subject (user), action (operation), resource, and environment. XACML identifies relevant policies and rules for computing decisions through a search for Targets (conditions that match the attributes of the request). Because multiple Policies in a PolicySet and/or multiple Rules in a Policy may produce conflicting access control decisions, XACML resolves these differences by applying a policy combining algorithm from a set defined by the standard. The entire process includes collecting attributes, matching conditions, computing rules, and resolving conflicts involving at least two data stores. There are two phases of policy evaluation that need to be considered. The first and costliest is loading policy from disk to Policy Decision Point (PDP) main memory, and the second is request evaluation. In both phases, performance is directly related to the number of policies considered. | 4.5 | | Arbitrary Data Service Operations and Policies ............................................"}], "metadata": {"source": "A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N", "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 Digital Identity Guidelines provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative.\nFor planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment\nperiods and provide feedback to NIST. Many NIST cybersecurity publications, other than\nthe ones noted above, are available at https://csrc.nist.gov/publications. Authority\n\nThis publication has been developed by NIST in accordance with its statutory\nresponsibilities under the Federal Information Security Modernization Act (FISMA)\nof 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible\nfor developing information security standards and guidelines, including minimum\nrequirements for federal information systems, but such standards and guidelines shall\nnot apply to national security systems without the express approval of appropriate\nfederal officials exercising policy authority over such systems. This guideline is consistent\nwith the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines\nmade mandatory and binding on federal agencies by the Secretary of Commerce\nunder statutory authority. Nor should these guidelines be interpreted as altering or\nsuperseding the existing authorities of the Secretary of Commerce, Director of the\nOMB, or any other federal official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\n(2017) An Introduction to Privacy Engineering and Risk Management in Federal Systems. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8062.\nhttps://doi.org/10.6028/NIST.IR.8062\n- [6] Joint Task Force Transformation Initiative (2011) Managing Information Security Risk: Organization, Mission, and Information System View. (National Institute of Standards and Technology, Gaithersburg, MD). NIST Special Publication (SP) 800-39. https://doi.org/10.6028/NIST.SP.800-39\n- [7] Joint Task Force (2018) Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-37 Rev. 2. https://doi.org/10.6028/NIST.SP.800-37r2\n- [8] Grassi PA, Garcia ME, Fenton JL (2017) Digital Identity Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63-3, Includes updates as of December 1, 2017. https://doi.org/10.6028/NIST.SP.800-63-3\n- [9] Office of Management and Budget (2017) Preparing for and Responding to a Breach of Personally Identifiable Information. (The White House, Washington, DC), OMB Memorandum M-17-12, January 3, 2017. Available at https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2017/m-17-12\\_0.pdf\n- [10] Joint Task Force Transformation Initiative (2013) Security and Privacy Controls for Federal Information Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-53, Rev. 4, Includes updates as of January 22, 2015. https://doi.org/10.6028/NIST.SP.800-53r4\n- [11] Grassi PA, Lefkovitz NB, Nadeau EM, Galluzzo RJ, Dinh AT (2018) Attribute Metadata: A Proposed Schema for Evaluating Federated Attributes. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8112."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Cyber Threat Information Sharing:\n\n- Indicators are technical artifacts or observables 1 that suggest an attack is imminent or is currently underway or that a compromise may have already occurred. Indicators can be used to detect and defend against potential threats. Examples of indicators include the Internet Protocol (IP) address of a suspected command and control server, a suspicious Domain Name System (DNS) domain name, a Uniform Resource Locator (URL) that references malicious content, a file hash for a malicious executable, or the subject line text of a malicious email message. - Tactics, techniques, and procedures (TTPs) describe the behavior of an actor. Tactics are high-level descriptions of behavior, techniques are detailed descriptions of behavior in the context of a tactic, and procedures are even lower-level, highly detailed descriptions in the context of a technique. TTPs could describe an actor's tendency to use a specific malware variant, order of operations, attack tool, delivery mechanism (e.g., phishing or watering hole attack), or exploit. - Security alerts , also known as advisories, bulletins, and vulnerability notes, are brief, usually humanreadable, technical notifications regarding current vulnerabilities, exploits, and other security issues. Security alerts originate from sources such as the United States Computer Emergency Readiness Team (US-CERT), Information Sharing and Analysis Centers (ISACs), the National Vulnerability Database (NVD), Product Security Incident Response Teams (PSIRTs), commercial security service providers, and security researchers. - Threat intelligence reports are generally prose documents that describe TTPs, actors, types of systems and information being targeted, and other threat-related information that provides greater situational awareness to an organization. Threat intelligence is threat information that has been aggregated, transformed, analyzed, interpreted, or enriched to provide the necessary context for decision-making processes."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Application Container Security Guide:\n\n3.5.4 不適切なユーザアクセス権 ... 3.5.4 不適切なユーザアクセス権\n\n対話型のユーザログオンはまれであるため、コンテナ専用 OS は通常、マルチユーザシナリオをサポートするように は最適化されていない。ユーザがコンテナを管理する目的では、オーケストレーションレイヤを経由してログオンす るよりも、直接ホストにログオンする際に、組織はよりリスクにさらされる。直接管理することで、システムとその 上にあるすべてのコンテナに対する広範な変更が可能になり、特定のアプリのコンテナを管理したいだけのユーザ が、他の多くのコンテナに影響を与えることが潜在的に可能となってしまう。\n\n## 3."}], "metadata": {"source": "Application Container Security Guide", "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 guidance does Guidelines on Security and Privacy in Public Cloud Computing provide?"}, {"role": "assistant", "content": "\n\n## Guidelines on Security and Privacy in Public Cloud Computing\n\nWayne Jansen Timothy Grance\n\n## NIST Special Publication 800-144\n\n## Guidelines on Security and Privacy in Public Cloud Computing\n\nWayne Jansen Timothy Grance\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nDecember 2011\n\n\n\n## U.S. Department of Commerce\n\nRebecca M. Blank, Acting Secretary\n\n## National Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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 discusses ITL's research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-144 80 pages (December 2011)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series:\n\n[44] Jonsson J (2006) On the Security of CTR + CBC-MAC. Selected Areas in Cryptography (SAC 2003), eds Nyberg K, Heys HM (Springer, Ottawa, Canada), Lecture Notes in Computer Science 2595, pp. 76-93.\nhttps://doi.org/10.1007/3-540-36492-7\\_7\n- [45] Joux A (2007) Authentication Failures in NIST version of GCM. Available at https://csrc.nist.gov/csrc/media/projects/block-ciphertechniques/documents/bcm/joux\\_comments.pdf\n- [46] Joux A, Martinet G, Valette F (2003) Blockwise-Adaptive Attackers Revisiting the (In)Security of Some Provably Secure Encryption Modes: CBC, GEM, IACBC. Advances in Cryptology (CRYPTO 2002), ed Moti Yung (Springer, Santa Barbara, CA), Lecture Notes in Computer Science 2442, pp. 17-30. https://doi.org/10.1007/3-540-45708-9\\_2\n- [47] Jutla CS (2004) Lower Bound on Linear Authenticated Encryption. Selected Areas in Cryptography (SAC 2004), eds Matsui M, Zuccherato RJ (Springer, Waterloo, Canada), Lecture Notes in Computer Science 3006, pp. 348-360. https://doi.org/10.1007/9783-540-24654-1\\_25\n- [48] Keller SS, Hall TA (2017) The Galois/Counter Mode (GCM) and GMAC Validation System (GCMVS) with the Addition of XPN Validation Testing. Available at https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-ValidationProgram/documents/mac/gcmvs.pdf"}], "metadata": {"source": "Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 1 – General:\n\n3.3.1 Communications versus Storage ... 3.3.1 | Public Authentication Keys... 3.3.1 Communications versus Storage\n\nKeys that are used for confidentiality protection of communication exchanges may often have shorter cryptoperiods than keys used for the protection of stored data."}], "metadata": {"source": "Recommendation for Key Management_ Part 1 – General", "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 Research Report_ User Perceptions of Smart Home Privacy and Security provide? (Part 5)"}, {"role": "assistant", "content": "| 17 | | | 3.2.8 | Device Hacking | 17 | | | 3.2.9 | Physical Safety | 18 | | | 3.2.10 | Other Security Concerns | 19 | | | 3.2.11 | Lack of Concern | 19 | | | 3.2.12 | Risk Acceptance | 20 | | 3.3 | Mitigations | Mitigations | 20 | | 4 Conclusion | 4 Conclusion | 4 Conclusion | 22 | | References | References | References | 22 | | List of Tables | List of Tables | List of Tables | List of Tables | | Table 1 Participant demographics | Table 1 Participant demographics | Table 1 Participant demographics | 4 | | Table 2 Privacy and security mitigations | Table 2 Privacy and security mitigations | Table 2 Privacy and security mitigations | 21 | | List of Figures | List of Figures | List of Figures | List of Figures | | Fig."}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 A Review of U.S. and European Security Evaluation Criteria:\n\nThe Orange Book forms the basis upon which the National Computer Security Center (NCSC) conducts its commercial computer security evaluation process. This process is focused on commercially produced and supported general-purpose operating system products that meet the needs of government departments and agencies. The evaluation is aimed at off-the-shelf products and is completely separate from any considerations of overall system performance, potential applications, or processing environments. The evaluation can provide a key input to a computer system security approval /accreditation . However, it does not constitute a complete computer system security study. A complete study must consider additional factors dealing with the system in its unique environment, such as its proposed security mode of operation, specific users, applications, data sensitivity, physical and personnel security, administrative security and communications security\n\nPart II describes a number of additional security services (e.g., communications integrity, denial of service, transmissions security) that arise in conjunction with networks. The full range of physical and administrative security measures appropriate to the highest sensitivity level of information on the network must be in place in order to operate a trusted network as described in the Red Book\n\nThe Red Book does not describe all the security requirements that may be imposed on a network. Depending upon the particular environment, there may be communications security, physical security, and other measures required."}], "metadata": {"source": "A Review of U.S. and European Security Evaluation Criteria", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\n| | • NIST SP 800-53 Rev.\n4 AU-4, CP-2, SC-5 • CCS CSC 17 |\n| | | PR.DS-5: Protections against data leaks are implemented | • COBIT 5 APO01.06 • ISA 62443-3-3:2013 SR 5.2 • ISO/IEC 27001:2013 A.6.1.2, A.7.1.1, A.7.1.2, A.7.3.1, A.8.2.2, A.8.2.3, A.9.1.1, A.9.1.2, A.9.2.3, A.9.4.1, A.9.4.4, A.9.4.5, A.13.1.3, A.13.2.1, A.13.2.3, A.13.2.4, A.14.1.2, A.14.1.3 • NIST SP 800-53 Rev. 4 AC-4, AC-5, AC-6, PE-19, PS-3, PS-6, SC-7, SC-8, SC-13, SC-31, SI-4 |\n| | | PR.DS-6: Integrity checking mechanisms are used to verify software, firmware, and information integrity | • ISA 62443-3-3:2013 SR 3.1, SR 3.3, SR 3.4, SR 3.8 • ISO/IEC 27001:2013 A.12.2.1, A.12.5.1, A.14.1.2, A.14.1.3 • NIST SP 800-53 Rev."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "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 Key Performance Indicators for Process Control System Cybersecurity Performance Analysis provide? (Part 5)"}, {"role": "assistant", "content": "...................10 | 4. Measurement Methodologies...............................................................................................10 | 4.\nMeasurement Methodologies...............................................................................................10 | |\n| 4.1. | 4.1. | Manufacturing Process Performance...............................................................................11 | |\n| 4.2. | 4.2. | Network Performance......................................................................................................12 | |\n| 4.3. | 4.3. | Computing Resources Performance.................................................................................12 | |\n| 4.4. | 4.4. | Industrial Protocol Performance......................................................................................13 | |\n| 4.5. | 4.5. | OPC Data Exchange Performance...................................................................................14 | |\n| 5. Appendix A -- References ....................................................................................................15 | 5."}], "metadata": {"source": "Key Performance Indicators for Process Control System Cybersecurity Performance Analysis", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2:\n\n3.5.1] with the following changes:\n\n1."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2", "cmmc_level": "2", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to A Review of U.S. and European Security Evaluation Criteria:\n\n* Division D; Minimal Protection -This division contains only one class. It is reserved for those systems that have been evaluated but that fail to meet the requirements for a higher evaluation class.\n* Division C: Discretionary Protection -Classes in this division provide discretionary (need-to-know) protection and, through the inclusion of audit capabilities, accountability of subjects and the actions they initiate.\n* Division B; Mandatory Protection -The concept of a security relevant or Trusted Computing Base (TCB) that preserves the integrity of sensitivity labels and uses them to enforce a set of mandatory access control rules\n\nis a major requirement of this division. Systems in this division must carry the sensitivity labels with major data structures in the system. The system developer also provides the security policy model on which the TCB is based and furnishes a specification of the TCB. Evidence must be provided to demonstrate that the reference monitor, an access control concept that refers to an abstract machine that mediates all accesses to objects by subjects, has been implemented. The security kernel, the hardware, software and firmware elements of a TCB, must mediate all accesses to data, be protected from modification, and be verifiable as correct.\n\nThe Orange Book addresses two types of access control discretionary and mandatory. Discretionary access control (DAC) is the weaker of the two. It provides a means of restricting access to objects based on the identity of subjects and/or groups to which they belong. The controls are discretionary in the sense that a subject with a certain access permission is capable of passing that permission, directly or indirectly, to any other subject. The TCB of Division C systems includes provisions for DAC. This type of access protection is vulnerable to Trojan horse attack and can result in security problems related to inappropriate or unauthorized sharing of objects."}], "metadata": {"source": "A Review of U.S. and European Security Evaluation Criteria", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Electronic Mail Security provide? (Part 2)"}, {"role": "assistant", "content": "y, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-45 Version 2 Natl. Inst. Stand. Technol. Spec. Publ. 800-45 Version 2, 139 pages (Feb.\n2007)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## Acknowledgements, Version 2\n\nThe authors, Wayne Jansen and Karen Scarfone of NIST, Miles Tracy of Federal Reserve Information Technology, and Jason Butterfield of Booz Allen Hamilton, wish to express their thanks to colleagues at both organizations who reviewed drafts of this document. In particular, their appreciation goes to Linda Antil, Rick Ayers, Bill Burr, Tim Grance, and Tim Polk from NIST for their research, technical support, and written contributions to this version of the document. The authors would also like to express their thanks to all those who contributed input during the public comment period and who assisted with our internal review process. ## Acknowledgements, Original Version\n\nThe authors, Wayne Jansen of NIST and Scott Bisker and Miles Tracy of Booz Allen Hamilton (BAH), wish to express their thanks to colleagues at both organizations who reviewed drafts of this document. In particular, their appreciation goes to John Wack, Murugiah Souppaya, and Tim Grance from NIST, and Steve Allison, Alexis Feringa, Jonathan Holleran, Kevin Kuhlkin, and Mark McLarnon from BAH, for their research, technical support, and written contributions to this document. The authors would also like to express their thanks to all those who contributed input during the public comment period and who assisted with our internal review process."}], "metadata": {"source": "Guidelines on Electronic Mail Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 U.S. Department of Justice Simplified Risk Analysis Guidelines:\n\n- a. A risk analysis may be defined as an analysis of the threats to and vulnerabilities of a system, expected losses, and selection of countermeasures to reduce the losses to an acceptable level. The requirement for Federal agencies to conduct a risk analysis of an Automated Data Processing (ADP) facility has been in effect since the issuance of the Office of Management and Budget (OMB) Circular A-71, Transmittal Memorandum No. 1 in 1978. The Department of Justice (DOJ) issued Order DOJ 2640. 2B and its earlier canceled versions which established the requirement for a risk analysis of DOJ ADP facilities beginning in 1977. The DOJ also issued a detailed risk analysis guidance document for use by DOJ ADP facilities in 1977. A number of Federal agencies, contractors, and university professors have developed risk analysis methodologies, some of which have been automated. Due to the complexity of the risk analysis process, the methodologies generally require considerable time to become knowledgeable of its correct usage and to complete the risk analysis. - b. A risk analysis does not enhance security by itself but provides cost effective security recommendations for management consideration. Therefore, there is a need to simplify the risk analysis process to the extent possible, which is the intent of the Simplified Risk Analysis Guidelines (SRAG) contained herein. The SRAG expedites the risk analysis process for the system under evaluation by initially determining if minimum security requirements applicable to the DOJ are met, which eliminates a number of threats and losses from evaluation. Although the SRAG simplifies the risk analysis process, SRAG users should be aware that significant effort by knowledgeable personnel may be required to complete a risk analysis."}], "metadata": {"source": "U.S. Department of Justice Simplified Risk Analysis Guidelines", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Foundations of a Security Policy for Use of the National Research and Educational Network:\n\n## Foundations of a Security Poiicy for Use of the- Nationai Research and Educationai Network\n\n## Foundations of a Security Policy for Use of the National Research and Educational Network\n\nSecurity has become a topic of national importance as more and more information is being processed in distributed computer systems and networks. This report explores some underlying considerations in the development of a security policy for the evolving National Research and Education Network (NREN)."}], "metadata": {"source": "Foundations of a Security Policy for Use of the National Research and Educational Network", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.1.2 | Time Spent on Security Awareness ... 3.1.2 Time Spent on Security Awareness\n\n## Focus Groups\n\nThe focus group demographic survey asked what percentage of time participants spend on their security awareness duties."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Computer Security Division 2007 Annual Report provide?"}, {"role": "assistant", "content": "## Computer Security Division 2007 Annual Report ## TAble of ConTenTS | Welcome | 1 | |--------------------------------------------------------------------------|-----| | Division Organization | 2 | | The Computer Security Division Responds to the | | | Federal Information Security Management Act of 2002 | 3 | | Security Management and Assistance | 4 | | FISMA Implementation Project | 4 | | Publications | 7 | | Outreach and Awareness | 11 | | Health Information Technology | 15 | | Security Testing and Metrics | 17 | | Validation Programs and Laboratory Accreditation | 17 | | Cryptographic Validation Standards | 20 | | Security Technology | 22 | | Cryptographic Standards Toolkit | 22 | | Response to Quantum Computing | 24 | | Authentication | 25 | | Security Aspects of Electronic Voting | 25 | | Systems and Network Security | 26 | | Identity Management | 26 | | Research in Emerging Technologies | 30 | | Automated Vulnerability Management and Measurement | 33 | | Infrastructure Services, Protocols, and Applications | 37 | | Biometrics | 44 | | CSD's Role in National and International IT Security Standards Processes | 47 | |"}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Computer Security Division 2012 Annual Report:\n\n|\n| Security Outreach and Integration Group................ | 5 |\n| Security Testing, Validation, and Measurement Group...\n| 6 |\n| The Computer Security Division Implements the Federal Information Security Management Act of 2002......................................................7 | |\n| CSD's Programs/Projects for FY2012..................8 | |\n| CSD Work in National and International Standards....."}], "metadata": {"source": "Computer Security Division 2012 Annual Report", "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.2 (NIST 3.6.2)?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 1_ Overview:\n\n3.6.2 Many Controls Support Multiple Capabilities... 3.6.2 Many Controls Support Multiple Capabilities\n\nMost control items support more than one capability."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\ngement, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems.\nThe Special\nPublication 800-series reports on ITL’s research, guidelines, and outreach efforts in\ninformation system security, and its collaborative activities with industry, government,\nand academic organizations."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Mobile Device Forensics provide? (Part 5)"}, {"role": "assistant", "content": "ochester Institute of Technology and Daren Melson for their assistance on technical issues that arose in our work. The authors would also like to thank all others who assisted with our review process.\n| Table of Contents | Table of Contents | Table of Contents |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| TABLE OFCONTENTS.............................................................................................................V | TABLE OFCONTENTS.............................................................................................................V | |\n| LIST OF FIGURES....................................................................................................................VII | LIST OF FIGURES....................................................................................................................VII | |\n| LIST OFTABLES...................................................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Program Review for Information Security Management Assistance (PRISMA) provide?"}, {"role": "assistant", "content": "## NISTIR 7358\n\n## Program Review for Information Security Management Assistance (PRISMA)\n\nPauline Bowen Richard Kissel\n\n\n\n## NISTIR 7358\n\n## Program Review for Information Security Management Assistance (PRISMA)\n\n## Pauline Bowen Richard Kissel\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nJanuary 2007\n\n\n\nU.S. Department of Commerce Carlos M. Gutierrez, Secretary\n\nTechnology Administration\n\nRobert Cresanti, Under Secretary of Commerce for Technology\n\nNational Institute of Standards and Technology William Jeffrey, Director\n\n## Reports on Information Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) has the broad mission of supporting U.S. industry, government, and academia by promoting U.S. innovation and industrial competitiveness through advancement of information technology measurement science, standards, and technology in ways that enhance economic security and improve our quality of life. ITL researchers have developed detailed protocols and operational standards that improve safety of their operation, and established assessment criteria and test data sets for validation of industrial products. ITL formulates metrics, tests, and tools for a wide range of subjects such as information complexity and comprehension, high confidence software, space-time coordinated mobile and wireless computing, as well as, issues of information quality, integrity, and usability. Under the Federal Information Security Management Act, ITL is directed to develop cyber security standards, guidelines, and associated methods and techniques. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of non national-securityrelated information in federal information systems."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Cyber Threat Information Sharing:\n\n| Type of Threat Information | Examples of Sensitive Data Elements 9 | Recommendations | |------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Network Indicators | Any single network indicator can be sensitive, but network indicators in the aggregate are often more sensitive because they can reveal relationships between network entities."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Liquefied Natural Gas:\n\n| Category........................................................................................................................................23 |\n| Table 22.\nCSF Subcategory Priorities for the Identify Function's Business Environment (ID.BE) Category........................................................................................................................................23 | |\n| Table 23. CSF Subcategory Priorities for the Identify Function's Governance (ID.GV) Category. .......................................................................................................................................................24 | |\n| Table 24. CSF Subcategory Priorities for the Identify Function's Risk Assessment (ID.RA) Category........................................................................................................................................24 | |\n| Table 25. CSF Subcategory Priorities for the Identify Function's Risk Management Strategy (ID.RM) | Category..........................................................................................................................25 |\n| Table 26. CSF Subcategory Priorities for the Identify Function's Supply Chain Management (ID.SC) Category."}], "metadata": {"source": "Cybersecurity Framework Profile for Liquefied Natural Gas", "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 2017 NIST_ITL Cybersecurity Program Annual Report:\n\nNo doubt that is because every year brings more troubling reports of organizations experiencing financial and reputational damage from both novel and well-known threats and vulnerabilities. But what does not get nearly as much attention are the impressive advances that so many organizations have been making in thoughtfully and successfully securing their information and processes and the systems upon which those organizations, their leaders, and their customers depend. This report features some of our most significant accomplishments during Fiscal Year (FY) 2017 in risk management, cryptography, identity and access management, vulnerability management, education and workforce development, and internet and communications infrastructure, as well as our efforts to transition our work into common practice. Below are just a few highlights of the work carried out in 2017. - NIST improved two widely used guidelines that provide senior leaders with the information they need to make risk-based decisions affecting critical mission and business functions. We proposed revisions to Security and Privacy Controls for Information Systems and Organizations (Special Publication (SP) 800-53) and Risk Management Framework for Information Systems and Organizations (SP 800-37). The latter provides a closer link between risk management processes and activities at various organizational levels. It demonstrates how the Cybersecurity Framework can be implemented using established Risk Management Framework processes. Both publications will be finalized in 2018."}], "metadata": {"source": "2017 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Information System Security Best Practices for UOCAVA-Supporting Systems:\n\nIT systems used to provide these functions face a variety of threats. If IT systems are not selected, configured and managed using security practices commensurate with the importance of the services they provide and the sensitivity of the data they handle, a security compromise could carry consequences for the integrity of the election and the confidentiality of sensitive voter information. Failure to adequately address threats to these systems could prevent voters from casting ballots, expose individuals to identity fraud, or even compromise the results of an election.\n\nThis document follows NISTIR 7551, A Threat Analysis on UOCAVA Voting Systems , which documents the threats to UOCAVA voting systems using electronic technologies for all aspects of the remote voting process. While NISTIR 7551 discusses high-level security controls capable of mitigating threats, the focus of that report was identifying technologies and associated risks. This document complements NIST 7551 by providing security best practices to help jurisdictions create UOCAVA voting systems based on security practices used in other IT applications.\n\nThere are many different ways to support UOCAVA voters, and each jurisdiction must put together its own system for such support. This document covers some common parts of UOCAVA system architectures, and shows how to secure those parts against both normal and extraordinary threats. The two components that are covered in most detail are Internet-based or Internet-assisted delivery of blank ballots and voter registration."}], "metadata": {"source": "Information System Security Best Practices for UOCAVA-Supporting 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 additional guidance does PDA Forensic Tools_ an Overview and Analysis provide? (Part 2)"}, {"role": "assistant", "content": "nology Interagency Report 67 pages (2004)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.\nSuch 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. ## Abstract\n\nDigital handheld devices, such as Personal Digital Assistants (PDAs), are becoming more affordable and commonplace in the workplace. They provide highly mobile data storage in addition to computational and networking capabilities for managing appointments and contact information, reviewing documents, communicating via electronic mail, and performing other tasks. Individuals can store and process personal and sensitive information independently of a desktop or notebook computer, and optionally synchronize the results at some later time. As digital technology evolves, the capabilities of these devices also continues to improve rapidly, taking advantage of new forms of removable media, faster processors that consume less power, touch screens with higher pixel resolution, and other components designed specifically for mobile devices. When handheld devices are involved in a crime or other incident, forensic examiners require tools that allow the proper retrieval and speedy examination of information present on the device. This report gives an overview of current forensic software, designed for acquisition, analysis, reporting of data discovered on PDAs, and an understanding of their capabilities and limitations."}], "metadata": {"source": "PDA Forensic Tools_ an Overview and Analysis", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Attribute Considerations for Access Control Systems 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-205 Natl. Inst. Stand. Technol. Spec. Publ. 800-205, 42 pages (June 2019) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-205\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": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 SRI International_ Improving the Security of Your UNIX System:\n\n| 3 | MONITORING SECURITY | 25 |\n|-------------|--------------------------------------|------|\n| 3 . 1 | Account Security | 25 |\n| 3.1.1 | The lastlog File | 25 |\n| 3.1.2 | The utmp and wtmp Files | 25 |\n| 3.1.3 | The acct File | 26 |\n| 3.2 | Network Security | 27 |\n| 3.2.1 | The syslog Facility | 27 |\n| 3.2.2 | The showmount Command | 28 |\n| 3.3 | File System Security | 29 |\n| 3.3.1 | The find Comm and | 29 |\n| 3.3. 1.1 | Finding Setuid and Setgid Files | 29 |\n| 3.3. 1.2 | Finding World-Writable Files | 31 |\n| 3 .3 . 1 .3 | Finding Unowned Files | 31 |\n| 3.3. 1.4 | Finding .rhosts Files | 31 |\n| 3.3.2 | Checklists | 32 |\n| 3.3.3 | Backups | 33 |\n| 3.4 | Know Your System | 33 |\n| 3.4.1 | The ps Command | 33 |\n| 3.4.2 | The who and w Commands | 34 |\n| 3.4.3 | The Is Command | 34 |\n| 3.5 | Keep Your Eyes Open | 34 |\n| 4 | SOFTWARE FOR IMPROVING SECURITY | 35 |\n| 4.1 | Obtaining Fixes and New Versions | 35 |\n| 4.1.1 | Sun Fixes on UUNET | 35 |\n| 4.1.2 | Berkeley Fixes | 36 |\n| 4."}], "metadata": {"source": "SRI International_ Improving the Security of Your UNIX System", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Obtaining Assurances for Digital Signature Applications:\n\nA digital signature is an electronic analogue of a written signature; the digital signature can be used to provide assurance that the claimed signatory signed the information. In addition, a digital signature may be used to detect whether or not the information was modified after it was signed (i.e., to detect the integrity of the signed data). Each signatory has a public and private key and is the owner of that key pair. The private key is used by the owner to generate a digital signature; the public key is used in the signature verification process. | Assurance of domain parameter validity | Assurance of the arithmetic validity of the domain parameters. |\n|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Assurance of possession | Assurance that the owner or claimed signatory actually possesses the private signature key. |\n| Assurance of public key validity | Assurance of the arithmetic validity of the public key. |\n| Assurance- signature | A digital signature on a private-key-possession assurance message. |\n| assurance_time | The time at which assurance of possession is obtained. |\n| Certificate | A set of data that uniquely identifies a key pair owner that is authorized to use the key pair, contains the owner's public key and possibly other information, and is digitally signed by a Certification Authority (i.e., a trusted party), thereby binding the public key to the owner. |\n| Certification Authority (CA) | The entity in a Public Key Infrastructure (PKI) that is responsible for issuing certificates and exacting compliance with a PKI policy."}], "metadata": {"source": "Recommendation for Obtaining Assurances for Digital Signature Applications", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide for Cybersecurity Event Recovery provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-184\n\n## Guide for Cybersecurity Event Recovery\n\nMichael Bartock Jeffrey Cichonski Murugiah Souppaya Matthew Smith Greg Witte Karen Scarfone\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-184\n\nC O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-184\n\n## Guide for Cybersecurity Event Recovery\n\nMichael Bartock Murugiah Souppaya Computer Security Division Information Technology Laboratory\n\nMatthew Smith Greg Witte G2, Inc. Annapolis Junction, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-184\n\nDecember 2016\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology\n\nJeffrey Cichonski Applied Cybersecurity Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official."}], "metadata": {"source": "Guide for Cybersecurity Event Recovery", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cloud Computing Synopsis and Recommendations:\n\nReliability refers to the probability that a system will offer failure-free service for a specified period of time within the bounds of a specified environment. For the cloud, reliability is broadly a function of the reliability of four individual components: (1) the hardware and software facilities offered by providers, (2) the provider's personnel, (3) connectivity to the subscribed services, and (4) the consumer's personnel. -  Legal. Consumers should investigate whether a provider can support ad hoc legal requests for: (1) eDiscovery, such as litigation freezes, and (2) preservation of data and meta-data. -  Operating Policies. Consumers should ascertain the operating policies of providers for their: (1) willingness to be subjected to external audits and security certifications, (2) incident response and recovery procedures/practices, including forensic analysis capabilities, (3) internal investigation processes with respect to illegal or inappropriate usage of IT resources, and (4) policies for vetting of privileged uses such as the provider's system and network administrators. -  Acceptable Use Policies. Consumers should ensure that all consumer personnel read and understand the provider's acceptable use policy, and negotiate an agreement for resolution of specific classes of policy violations in advance with the provider. Further, it is important that consumers know the process a priori for how disputes over possible policy violations will be resolved between themselves and the provider. -  Licensing. Consumers should ensure that both the provider and consumer properly license any proprietary software installed into a cloud. -  Patch Management."}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "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.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Practical Combinatorial Testing:\n\n3.3.2 Cost Factors\n\nUsing combinatorial methods to design test configurations is probably the most widely used combinatorial approach because it is quick and easy to do and typically delivers significant improvements to testing."}], "metadata": {"source": "Practical Combinatorial Testing", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\n'For our main enterprise network, it's computer-based training that's taken annually…But for those who don't have access to the enterprise network often for certain other networks that we might maintain,…those are physical briefings done by the ISSOs [information system security officers] to those personnel. And then they sign an acknowledgment form.' (D03)\n\n'You've got IT security, physical security, personnel security, etc. And they have their own training requirements…It's inefficient.' (S11)"}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. This publication provides security and privacy control baselines for the Federal Government. There are three security control baselines (one for each system impact level-low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level. In addition to the control baselines, this publication provides tailoring guidance and a set of working assumptions that help guide and inform the control selection process."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Computer Security Division 2006 Annual Report provide? (Part 3)"}, {"role": "assistant", "content": "00-53A, Guide for Assessing the Security Controls in Federal Information Systems ; and publication of FIPS 200, Minimum Security Requirements for Federal Information and Information Systems .\nThe Cryptographic Module Validation Program was expanded to include 13 laboratories in 4 countries and continues to ensure the protection of sensitive information in computer and telecommunication systems, including voice systems. Research and development efforts included security for Radio Frequency IDentification (RFID) devices and other wireless communications systems, digital forensic tools and methods, Internet security protocols, and expansion of the National Vulnerability Database. We will continue to strive to provide products and services that protect and enhance confidence in the nation's information technology systems."}], "metadata": {"source": "Computer Security Division 2006 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Trustworthy Email:\n\n(MP) | | MP-1 | MEDIA PROTECTION POLICY AND PROCEDURES | MP-1 | MP-1 | MP-1 | | MP-2 | MEDIA ACCESS | MP-2 | MP-2 | MP-2 | | MP-3 | MEDIA MARKING | - | MP-3 | MP-3 | | MP-4 | MEDIA STORAGE | - | MP-4 | MP-4 | | MP-5 | MEDIA TRANSPORT | - | MP-5 (4) | MP-5 (4) |"}], "metadata": {"source": "Trustworthy Email", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines for the Secure Deployment of IPv6:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | 1 |\n|--------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|\n| | Introduction ................................................................................................................... | Introduction ..................................................................................................................."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Vulnerability Management:\n\n3.1.2 | 3. 3.1.2 Adapt Roles to the Organization\n\nThe sub-steps for adapting roles to the organization are described in this section."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Vulnerability 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 additional guidance does Mobile Forensic Reference Materials_ a Methodology and Reification provide? (Part 2)"}, {"role": "assistant", "content": "nology Interagency Report 35 pages (2009)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately.\nSuch 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 . ## Abstract\n\nThis report concerns the theoretical and practical issues with automatically populating mobile devices with reference test data for use as reference materials in validation of forensic tools. It describes an application and data set developed to populate identity modules and highlights subtleties involved in the process. Intriguing results attained by recent versions of commonlyused forensic tools when used to recover the populated data are also discussed. The results indicate that reference materials can be used to identify a variety of inaccuracies that exist in present-day forensic tools. Keywords: Mobile Devices, Computer Forensics, Forensic Tool Validation\n\n## Table of Contents\n\n| 1. | Introduction............................................................................................................................1 | Introduction............................................................................................................................1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|\n| 2."}], "metadata": {"source": "Mobile Forensic Reference Materials_ a Methodology and Reification", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems:\n\nproposed. The software can be managed by the developers as an open-source project shared publicly using version control platforms, such as Github, or the software can be proprietary and kept private.\nDevelopment patterns can be leveraged to enable smart contract upgradability (e.g., a registry contract that points to the latest version of the main contract of the system or an interface contract that is inherited by the system and defines a set of key functions and parameters). Periodic thirdparty audits, automated tests, and reports can also be performed and disclosed to help assess whether the rules are properly enforced."}], "metadata": {"source": "A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\n| Function | Category | Subcategory | Informative References |\n|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| IDENTIFY (ID) | Asset Management (ID.AM): The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to business objectives and the organization's risk strategy. | ID.AM-1 : Physical devices and systems within the organization are inventoried | • CCS CSC 1 • COBIT 5 BAI09.01, BAI09.02 • ISA 62443-2-1:2009 4.2.3.4 • ISA 62443-3-3:2013 SR 7.8 • ISO/IEC 27001:2013 A.8.1.1, A.8.1.2 • NIST SP 800-53 Rev."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1:\n\n3.2.5 Allowed Check System Usage ... 3.2.5 Allowed Check System Usage\n\nThe following requirements and recommendations apply to the use of the <xccdf:check> and <xccdf:complex-check> elements:\n\n1. 3.2.5."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "cmmc_level": "2", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers:\n\nct levels, as described in FIPS 199 and SP 800-53. Developers are also encouraged to consider requirements imposed by the Health Insurance Portability and Accountability Act (HIPAA) and other sources.\n| Field Name | Description |\n|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Target Operational Environment | The IT product's operational environment, such as Standalone, Managed, or Custom (with description, such as Specialized Security-Limited Functionality, Legacy, or United States Government). Generally only applicable for security compliance/vulnerability checklists. |\n| Checklist Type | The type of checklist, such as Compliance, Vulnerability, and Specialized."}], "metadata": {"source": "National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers", "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 Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security Division 2010 Annual Report:\n\nsystems for potential federal agency use: hosted a growing repository of federal agency security practices, public/private security practices, and security configuration checklists for IT products.\nCon-\n\nIn addition to the above publications, the division collabo rated with the Manufacturing Engineering Laboratory at NIST in reviewing comments received and updating the draft guide to industrial control system security, NIST SP 800-82, G uide to Industrial Control Systems (ICS) Security: Supervisory Control and Data Acquisition (SCADA) Systems, Distributed Control Systems (DCS), and Other Control System Configurations Such as Programmable Logic Controllers (PLC) ."}], "metadata": {"source": "Computer Security Division 2010 Annual Report", "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 PIV Data Model Test Guidelines provide? (Part 3)"}, {"role": "assistant", "content": "V logical credentials. Such components include biometric elements in the form of fingerprint information and facial imagery and security elements such as electronic keys, certificates, and signatures.\nFIPS201 incorporates by reference NIST Special Publication 800-73 (SP80073), which specifies elements related to the PIV card interface, NIST Special Publication 800-76 (SP80076), which specifies the biometric requirements, and NIST Special Publication 800-78 (SP80078) which specifies acceptable cryptographic algorithms and key sizes for PIV systems. A robust testing framework and guidance to provide assurance that a particular component or system is compliant with FIPS201 and supporting standards should exist to build the necessary PIV infrastructure to support common unified processes and systems for government-wide use. NIST developed test guidance in two parts. The first part addresses test requirements for interface to the PIV card and are provided in SP80085A. The second part provides test requirements for the PIV data model and is provided in this document. This document specifies the derived test requirements, and the detailed test assertions and conformance tests for testing the PIV data model. ## Table of Contents\n\n| 1."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Research Report_ User Perceptions of Smart Home Privacy and Security:\n\n3.2.1 | Audio and Video Access | 12 |\n| | 3. 3.2.10 | Other Security Concerns | 19 |\n| | 3. 3.2.12 | Risk Acceptance | 20 |\n| 3."}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management:\n\n3.4.3 High Baseline Control Allocation Table... 3.4.3 Control Item CM-2(7)(a): BASELINE CONFIGURATION | CONFIGURE SYSTEMS, COMPONENTS, OR DEVICES FOR HIGH-RISK AREAS\n\n## Control Item Text:\n\nThe organization:\n\n- (a) Issues [Assignment: organization-defined systems, system components, or devices] with [Assignment: organizationdefined configurations] to individuals traveling to locations that the organization deems to be of significant risk. 3.4.3 High Baseline Control Allocation Table\n\nTable 10: High Baseline Control (Item) Allocation Table\n\n| Impact Level | Determination Statement ID | Implemented By | Assessment Boundary | Assessment Responsibility | Assessment Methods | Selected | Rationale for Risk Acceptance | Frequency of Assessment | Impact of not implementing |\n|----------------|------------------------------|------------------|-----------------------|-----------------------------|----------------------|------------|---------------------------------|---------------------------|------------------------------|\n| 3 | CM-3(1)(a)(1) DSM | | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | CM-3(1)(b)(1) | ISCM-Sys | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | CM-3(1)(c)(1) | ISCM-Sys | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | CM-3(1)(d)(1) | ISCM-Sys | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | CM-3(1)(e)(1) | ISCM-Sys | TBD | MAN | TBD | | | | |\n| 3 | CM-3(1)(f)(1) | ISCM-Sys | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | CM-8(2)(1) | ISCM-Sys | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | MA-3(3)(a)(1) | DM | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | MA-3(3)(b)(1) | DM | ISCM-TN | ISCM-Sys | Test | | | | |\n| 3 | SA-12(1) | DSM | ISCM-TN | ISCM-Sys | Test | | | | |\n\nAUTOMATION SUPPORT FOR SECURITY ASSESSMENTS: HWAM\n\n## Appendix A."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Information Technology Security Services:\n\n- ƒ SP 800-30: Risk Management Guide for Information Technology Systems - ƒ SP 800-32: Introduction to Public Key Technology and the Federal PKI Infrastructure - ƒ SP 800-33: Underlying Technical Models for Information Technology Security - ƒ SP 800-34: Contingency Planning for Information Technology Systems - ƒ SP 800-41: An Introduction to Firewalls and Firewall Policy - ƒ SP 800-42: Guideline on Network Security Testing - ƒ SP 800-48: Wireless Network Security: 802.11, Bluetooth, and Handheld Devices - ƒ SP 800-50: Building an Information Technology Security Awareness and Training Program - ƒ SP 800-53: Recommended Security Controls for Federal Information Systems | Types | of Services.............................................................................................................5-1 | of Services.............................................................................................................5-1 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 5.1 | | Management Security Services ...............................................................................5-2 | | | 5.1.1 | IT Security Program Development ...............................................................5-2 | | | 5.1.2 | IT Security Policy..........................................................................................5-3 | | | 5.1.3 | Risk Management ........................................................................................5-4 | | | 5.1.4 | IT Security Architecture ................................................................................5-4 | | | 5.1.5 | Certification and Accreditation......................................................................5-4 | | | 5.1.6 | IT Security Product Evaluation.....................................................................5-5 | | 5.2 | Operational Security Services..................................................................................5-6 | Operational Security Services..................................................................................5-6 | | | 5.2.1 | Contingency Planning ..................................................................................5-6 | | | 5.2.2 | Incident Handling..........................................................................................5-7 | |"}], "metadata": {"source": "Guide to Information Technology Security Services", "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 Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992:\n\n- Establish configuration control for security purposes (Priority A).\n- -Supercomputer sites are high priority.\n- -Distribute/support use of automated security management tools (e.g. COPS).\n- Establish a security perimeter protection capability (Priority B) (e.g. filters, control gateways, Simple Network Management Protocol (SNMP)).\n- Establish security audit information collection and review capability (Priority B).\n\n1. use of stronger methods to tighten access controls, ranging from more rigorous administration of passwords to automated mechanisms such as token-based systems, one-time passwords, and perhaps smart cards;\n2. use of front-end filters for cost-effective perimeter control, e.g. routers with access control lists, specialized gateways and front-end boxes;\n3. use of audit trails with logs of relevant security events;\n4. use of tools for storage of information in tamper-resistant ways;\n\nThe ASACS authentication sequence for logging onto a machine with a R/W can be implemented in a number of different ways. In the NIST approach, the host machine would first reset the card and then prompt the user for the PIN which has to be sent to the card. The user is authenticated to the card by entering the correct PIN, either through the keypad on the portable R/W or on a keyboard via the host machine. The former path is considered more secure. The card sends back an authentication number that the user can look at to determine whether it is the the right card. This is not considered a strong security mechanism it is similar to writing your name on a card and having it embossed."}], "metadata": {"source": "Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992", "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 A Framework for Designing Cryptographic Key Management Systems:\n\nkey or key pair and whose identifier is associated with a cryptographic key or key pair. For publicprivate key pairs, the association is typically established through a registration process.\nA symmetric key may have a single specific owner, or multiple owners may share the key. - g) CKMS User: CKMS users utilize the CKMS when key management functions are required to support an application. CKMS users may be, and often are, key owners."}], "metadata": {"source": "A Framework for Designing Cryptographic Key Management 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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Computer Security Log Management:\n\n| Authority................................................................................................................\n| 1-1 |\n| | 1.2 | Purpose and Scope............................................................................................... | 1-1 |\n| | 1.3 | Audience............................................................................................................... | 1-1 |\n| | 1.4 | Publication Structure ............................................................................................. | 1-1 |\n| 2. | Introduction | to Computer Security Log Management ................................................"}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Fiscal Year 2022 Cybersecurity and Privacy Annual Report:\n\n| Cryptography | 7 |\n|---------------------------------------------|-----|\n| Education, Training & Workforce Development | 9 |\n| Identity & Access Management | 11 |\n| Privacy | 13 |\n| Risk Management & Measurement | 15 |\n| Trustworthy Networks & Platforms | 17 |\n| Usable Cybersecurity | 19 |\n| NCCoE Summary | 21 |\n| Opportunities to Engage | |\n\n- The Post-Quantum Cryptography team announced the third-round selection and the fourth-round candidates. The call for additional signatures was released. Standards development on the selected algorithms is underway.\n- The Lightweight Cryptography Project continued to evaluate the finalist algorithms to prepare for the final selection. The fifth Lightweight Cryptography Workshop was held.\n- NIST's Crypto Publication Review Board completed two reviews, and seven reviews are in progress to update and modernize the portfolio of cryptographic standards.\n- NIST continued to explore multi-party threshold cryptography through workshops, calls for feedback on criteria for threshold schemes, and other industry collaboration.\n\nEnergizing, promoting, and coordinating the workforce are key priorities for NIST. The National Initiative for Cybersecurity Education (NICE) supports a robust community that works together to advance an integrated ecosystem of cybersecurity education, training, and workforce development."}], "metadata": {"source": "Fiscal Year 2022 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\nNISTIR 8183 Revision 1 updates the Manufacturing Profile to include the sub-category enhancements established in NIST Framework for Improving Critical Infrastructure Cybersecurity Version 1.1. These updates include managing cybersecurity within the supply chain, self-assessing cybersecurity risk, vulnerability disclosure, system integrity, and more comprehensive controls for identity management. Additional changes include updating language to change references from 'security levels' to 'impact levels.'\n\nManage cybersecurity risks that could adversely affect the quality of product. Protect against compromise of integrity of the manufacturing process and associated data.\n\n1. The potential impact is LOW if the loss of integrity, availability, or confidentiality could be expected to have a limited adverse effect on manufacturing operations, manufactured product, assets, brand image, finances, personnel, the general public, or the environment.\n2. The potential impact is MODERATE if the loss of integrity, availability, or confidentiality could be expected to have a serious adverse effect on manufacturing operations, manufactured product, assets, brand image, finances, personnel, the general public, or the environment.\n3. The potential impact is HIGH if the loss of integrity, availability, or confidentiality could be expected to have a severe or catastrophic adverse effect on manufacturing operations, manufactured product, assets, brand image, finances, personnel, the general public, or the environment."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Storage Encryption Technologies for End User Devices:\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.\n\nThe authors, Karen Scarfone and Murugiah Souppaya of the National Institute of Standards and Technology (NIST), and Matt Sexton of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. In particular, their appreciation goes to Tim Grance, Bill Burr, and Tim Polk of NIST, and Derrick Dicoi, Angela Orebaugh, Manuel Villar, Mike Zeberlein, and Mike Zirkle of Booz Allen Hamilton, for their keen and insightful assistance throughout the development of the document. The authors also appreciate the efforts of those individuals, agencies, and other organizations that contributed input during the public comment period."}], "metadata": {"source": "Guide to Storage Encryption Technologies for End User Devices", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Computer Security Division 2008 Annual Report:\n\nnd flexible approach for developing security assessment plans containing assessment procedures to determine the effectiveness of security controls deployed in federal information systems.\nAlso completed with NIST SP 800-53A, was an initial public draft of webbased assessment cases, which were developed by an interagency team to provide security assessors with online, worked examples identifying specific assessor action steps to accomplish for each of the assessment procedures in SP 800-53A;\n- Revision of NIST SP 800-60, which updates the information types used ◆◆ by agencies to develop information system impact levels to help determine the criticality and sensitivity of federal information systems."}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to The NIST Definition of Cloud Computing:\n\nCloud computing is an evolving paradigm. The NIST definition characterizes important aspects of cloud computing and is intended to serve as a means for broad comparisons of cloud services and deployment strategies, and to provide a baseline for discussion from what is cloud computing to how to best use cloud computing. The service and deployment models defined form a simple taxonomy that is not intended to prescribe or constrain any particular method of deployment, service delivery, or business operation.\n\nSoftware as a Service (SaaS). The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure 2 . The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based email), or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited userspecific application configuration settings.\n\nlanguages, libraries, services, and tools supported by the provider. 3 The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment."}], "metadata": {"source": "The NIST Definition of Cloud Computing", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.5.2. 3.5.2."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Vetting the Security of Mobile Applications:\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 contrast to static analysis, the most important dynamic analysis requirement is to see the workings of the code as it is being executed. There are two primary ways to obtain this information. First, an executing app can be connected to a remote debugger. Second, the code can be run on an emulator that has built-in debugging capabilities. Running the code on the intended mobile device allows the test tool to select the exact characteristics of the device and can provide a more accurate view about how the app will be behave. On the other hand, an emulator provides more control, especially when the emulator is open-source and can be modified by the evaluator to capture whatever information is needed. Although emulators can simulate different devices, they do not simulate all of them and therefore the simulation may not be completely accurate. Note that malware increasingly detects the use of emulators as a testing platform and changes its behavior accordingly to avoid detection."}], "metadata": {"source": "Vetting the Security of Mobile Applications", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n| 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.4.1. Enterprise Risk Management and C-SCRM Owners and Operators.............................................5 |\n| 1.4.2. Enterprise, Agency, and Mission and Business Process Owners and Operators .........................5 |\n| 1.4.3. Acquisition and Procurement Owners and Operators.................................................................6 |\n| 1.4.4. Information Security, Privacy, or Cybersecurity Operators .........................................................6 |\n| 1.4.5. System Development, System Engineering, and System Implementation Personnel.................7 |\n| 1.5.1. Enterprise's Supply Chain.............................................................................................................9 |\n| 1.5.2. Supplier Relationships Within Enterprises .................................................................................10 |\n| 2. Integration of C-SCRM Into Enterprise-Wide Risk Management...................................................... 18 |\n| 2.3.1. Roles and Responsibilities Across the Three Levels ...................................................................24 |\n| 2.3.2. Level 1 -Enterprise...................................................................................................................27 |\n| 2.3.3."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in\naccordance with its assigned statutory responsibilities. The information in this publication, including\nconcepts, practices, and methodologies may be used by federal agencies even before the completion of\nsuch companion publications. Thus, until each publication is completed, current requirements, guidelines,\nand procedures, where they exist, remain operative. For planning and transition purposes, federal\nagencies may wish to closely follow the development of these new publications by NIST. The National Institute of Standards and Technology (NIST) Information Technology Laboratory\n(ITL) promotes the U.S. economy and public welfare by providing technical leadership for the\nNation’s measurement and standards infrastructure. ITL develops tests, test methods, reference\ndata, proof of concept implementations, and technical analyses to advance the development\nand productive use of information technology (IT). ITL’s responsibilities include the development\nof management, administrative, technical, and physical standards and guidelines for the cost-\neffective security of other than national security-related information in federal information\nsystems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach\nefforts in information systems security and privacy and its collaborative activities with industry,\ngovernment, and academic organizations. This publication provides a methodology and set of procedures for conducting assessments of\nsecurity and privacy controls employed within systems and organizations within an effective risk\nmanagement framework. The assessment procedures, executed at various phases of the system\ndevelopment life cycle, are consistent with the security and privacy controls in NIST Special\nPublication 800-53, Revision 5."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\nactual state; assessment; authorization boundary; automation; capability; continuous diagnostics and mitigation; dashboard; defect; desired state specification; firmware; information security continuous monitoring; ISCM; inventory management; malicious code; malware; mitigation; mobile code; ongoing assessment; root cause analysis; security capability; security control; security control item; software; software asset management; software file; SWID tag; whitelisting.\n\nThe scope of this report is limited to security controls and control items that are implemented to manage the download, installation, and execution of unauthorized and malicious software (malware). 4 In this case, malware refers to known and unknown malicious code, including software that executes a zero-day attack.\n\n4 Malware, also known as malicious code, refers to a software program that is covertly inserted into another software program with the intent to destroy data, run destructive or intrusive software programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Source: Souppaya M., Scarfone K., (2013) (National Institute of Standards and Technology, Gaithersburg, MD), Guide to Malware Incident Prevention and Handling for Desktops and Laptops, NIST Special Publication (SP) 800-83, https://doi.org/10.6028/NIST.SP.800-83r1."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset 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 Media Protection?"}, {"role": "assistant", "content": "According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security:\n\n.....................................................1 | 1. Introduction .........................................................................................................................1 | 1.\nIntroduction .........................................................................................................................1 | |\n| | 1.1 | Purpose and Scope | ....................................................................................................1 |\n| | 1.2 | Audience.....................................................................................................................1 | |\n| | 1.3 | Document Structure....................................................................................................1 | |\n| 2."}], "metadata": {"source": "Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\n| DTR No: | DTR Description | Spec. Reference |\n|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|\n| DTR-06.01.01.01 | For a Universal Integrated Circuit Card (UICC) used to host a Derived PIV Application, the UICC shall implement the GlobalPlatform Card Secure Element Configuration v1.0 [GPSE]. | • [SP800-157], Section 3.3.1.2 - Removable UICC with Cryptographic Module |\n\n| DTR No: | DTR Description | Spec. Reference |\n|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------|\n| DTR-06.01.02.01 | For a USB Integrated Circuit(s) Card Device (ICCD) used to host a Derived PIV Application, the ICCD shall comply with the Universal Serial Bus Device Class - Smart Card ICCD Specification for USB Integrated Circuit(s) Card Devices [ICCDSPEC]."}], "metadata": {"source": "Derived PIV Application and Data Model Test 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 does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |\n\n## 03.01.06 Least Privilege - Privileged Accounts\n\n[SELECT FROM: access control policy and procedures; procedures for least privilege; list of system-generated privileged accounts; list of system administration personnel; system audit records; system configuration settings; system security plan; list of system-generated security functions or security-relevant information assigned to system accounts or roles; other relevant documents or records]"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security Division 2008 Annual Report:\n\nsystems for potential federal agency use - Hosted a growing repository of federal agency security practices, public/private security practices, and security configuration checklists for IT products.\nIn conjunction with the Government of Canada's Communications Security Establishment, CSD leads the Cryptographic Module Validation Program (CMVP). The Common Criteria Evaluation and Validation Scheme (CCEVS) and CMVP facilitate security testing of IT products usable by the federal government. - Solicit recommendations of the Information Security and Privacy ◆◆ Advisory Board on draft standards and guidelines - Solicited recommendations of the Board regularly at quarterly meetings. - Provide outreach, workshops, and briefings ◆◆ - Conducted ongoing awareness briefings and outreach to CSD's customer community and beyond to ensure comprehension of guidance and awareness of planned and future activities. CSD also held workshops to identify areas that the customer community wishes to be addressed, and to scope guidelines in a collaborative and open format. - Satisfy annual NIST reporting requirement ◆◆ - Produced an annual report as a NIST Interagency Report (IR). The 2003-2007 Annual Reports are available via our Computer Security Resource Center (CSRC) website or upon request."}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "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 Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\n| Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi |\n|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ............................................................................................................1 | 1. Introduction ............................................................................................................1 | |\n| | Purpose and Scope | ........................................................................................ 1 |\n| | Audience........................................................................................................."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "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.15 (NIST 3.1.15)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.15. 3.1.15."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.15", "cmmc_practice_id": "AC.L2-3.1.15", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\n\nFIPS 201 defines the requirements and characteristics of government-wide interoperable identity credentials. It specifies that these identity credentials must be stored on a smart card and that additional common identity credentials, known as derived PIV credentials, may be issued by a federal department or agency and used when a PIV Card is not practical. This document contains the technical specifications to interface with the smart card to retrieve and use the PIV identity credentials. The specifications reflect the design goals of interoperability and PIV Card functions. The goals are addressed by specifying a PIV data model, card edge interface, and application programming interface. Moreover, this document enumerates requirements for the options and branches in international integrated circuit card standards. The specifications go further by constraining interpretations of the normative standards to ease implementation, facilitate interoperability, and ensure performance in a manner tailored for PIV applications.\n\nFIPS 201 defines processes for binding identities to authenticators, such as the PIV Card and derived PIV credentials used in the federal PIV system. SP 800-73-5 contains the technical specifications to interface with the PIV Card to retrieve and use the identity credentials. The specifications reflect the design goals of interoperability and PIV Card functions. The goals are addressed by specifying a PIV data model, card edge interface, and application programming interface. Moreover, this document enumerates requirements for the options and branches in international integrated circuit card (ICC) standards [ISO7816]. The specifications go further by constraining interpretations of the normative standards to ease implementation, facilitate interoperability, and ensure performance in a manner tailored for PIV applications.\n\n## 3.2. Entry Points for Data Access"}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security:\n\n| Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi |\n|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction .........................................................................................................................1 | 1. Introduction .........................................................................................................................1 | 1."}], "metadata": {"source": "Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Forensics Web Services (FWS):\n\nYet another important principle that any evidence should have is reliability. In the court of law, digital evidence must be presented in an articulate manner. Because impersonation and replay attacks do occur in web services, cryptographic mechanisms would help to protect ownership of information passed around in messages by signing them digitally. Such a requirement, of course, would entail web services using a cryptography platform such as Public Key Infrastructure (PKI). Robinson [12] influenced the model employed through FWS for pair-wise evidence generation with some differences. Robinson [12] provides a framework to support fair B2B communications\n\n- [1] A. Vorobiev and H. Jun, \"Security Attack Ontology for Web Services,\" in Semantics, Knowledge and Grid, 2006. SKG '06. Second International Conference on , 2006, pp. 4242. - [2] Y. Demchenko, L. Gommans, C. de Laat, and B. Oudenaarde, \"Web services and grid security vulnerabilities and threats analysis and model,\" in Grid Computing, 2005. The 6th IEEE/ACM International Workshop on , 2005, p. 6 pp. - [3] A. Singhal, T. Winograd, and K. Scarforne, NIST Special Publication 800-95, \"Guide to Secure Web Services' , August 2007, http://csrc.nist.gov/publications/nistpubs/80095/SP800-95.pdf. - [4] R. Khalaf, N. Mukhi, and S. Weerawarana, \"Service-Oriented Composition in BPEL4WS,\" in Twelfth International World Wide Web Conference , Budapest, Hungary, 2003. - [5] S. M. S. Cruz, M. L. M. Campos, P. F. Pires, and L. M. Campos, \"Monitoring e-business Web services usage through a log based architecture,\" in Web Services, 2004. Proceedings. IEEE International Conference on , 2004, pp. 61-69. - [6] A. Herzberg and I. Yoffe, \"The Delivery and Evidences Layer,\" Cryptology ePrint Archive Report 2007/139, 2007. - [7] S. Kremer, O. Markowitch, and J. Zhou, \"An Intensive Survey of Non-repudiation protocols,\" Computer Communications, vol. 25, pp. 1606-1621, 2002. - [8] P."}], "metadata": {"source": "Forensics Web Services (FWS)", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.15 (NIST 3.1.15)?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\n3.1.15 Sensitive Data Protection Vulnerability (CWE-199)\n\nDescription\n\nOWASP describes the sensitive data protection vulnerability as follows:\n\nThis category is for tagging vulnerabilities that lead to insecure protection of sensitive\ndata."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "nist_control": "3.1.15", "cmmc_practice_id": "AC.L2-3.1.15", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n\n\n## NIST Internal Report NIST IR 8323r1\n\n## Foundational PNT Profile: Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services\n\nMichael Bartock\n\nJoseph Brule\n\nYa-Shian Li-Baboud\n\nSuzanne Lightman\n\nJames McCarthy\n\nKarri Meldorf\n\nKaren Reczek\n\nDoug Northrip\n\nArthur Scholz\n\nTheresa Suloway\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8323r1\n\n\n\n## NIST Internal Report NIST IR 8323r1\n\n## Foundational PNT Profile: Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services\n\nMichael Bartock Suzanne Lightman Computer Security Division Information Technology Laboratory\n\nYa-Shian Li-Baboud\n\nSoftware Systems Division Information Technology Laboratory\n\nJames McCarthy Applied Cybersecurity Division Information Technology Laboratory\n\nKaren Reczek Standards Coordination Office Laboratory Programs\n\nJoseph Brule Karri Meldorf Doug Northrip Arthur Scholz Theresa Suloway The MITRE Corporation\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8323r1\n\nJanuary 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. 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": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Security Segmentation in a Small Manufacturing Environment provide?"}, {"role": "assistant", "content": "\n\n## NIST Cybersecurity White Paper NIST CSWP 28\n\n## Security Segmentation in a Small Manufacturing Environment\n\nDr. Michael Powell National Cybersecurity Center of Excellence National Institute of Standards and Technology\n\nJohn Hoyt Aslam Sherule Dr. Lynette Wilcox The MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.CSWP.28\n\nApril 6 , 2023\n\n\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## 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 2023-03-3 0\n\n## How to Cite this NIST Technical Series Publication:\n\nPowell M, Hoyt J, Sherule A, Wilcox L (202 3 ) Security Segmentation in a Small Manufacturing Environment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 28. https://doi.org/10.6028/NIST.CSWP.28\n\n## Author ORCID iDs\n\nDr. Michael Powell: 0000-0002-3922-7435 John Hoyt: 0000-0002-0783-7036 Aslam Sherule: 0000-0002-2003-3817 Dr. Lynette Wilcox: 0000-0003-1246-6505\n\n## Contact Information\n\nmanufacturing\\_nccoe@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). ## Abstract\n\nManufacturers are increasingly targeted in cyber-attacks."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171r2 (February 2020; Includes updates as of 01-28-2021) https://doi.org/10.6028/NIST.SP.800-171r2\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\n3.1.4. 3.1.4."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Standard Security Label for GOSIP_ an Invitational Workshop:\n\n3.1.1 The impact of the sweeping revisions to the identification of sensitive information varied among the federal departments."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Computer Security Division 2012 Annual Report:\n\n| Table of Contents | ........................................ iii |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|\n| Welcome Letter | ...........................................1 |\n| Division Organization | ....................................2 |\n| Intro to CSD's 5 Groups | ..................................3 |\n| Cryptographic Technology Group | .......................... 3 |\n| Security Components and Mechanisms Group........... | 4 |\n| Secure Systems and Applications Group.................. | 4 |\n| Security Outreach and Integration Group................ | 5 |\n| Security Testing, Validation, and Measurement Group..."}], "metadata": {"source": "Computer Security Division 2012 Annual Report", "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 PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance):\n\nINTRODUCTION.....................................................................................................................1 | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| | 1.1 | | PURPOSE ............................................................................................................................1 | | | 1.2 | | SCOPE ................................................................................................................................1 | | | 1.3 | | TARGET AUDIENCE | ............................................................................................................2 | | | 1.4 | DOCUMENT OVERVIEW......................................................................................................3 | | | 2."}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "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.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Guide for Security-Focused Configuration Management of Information Systems:\n\n3.3.1 IMPLEMENT ACCESS RESTRICTIONS FOR CHANGE\n\nAccess restrictions for change represent the enforcement side of SecCM. 3.3.1 Handling of Scheduled, Unscheduled, and Unauthorized Changes\n- 3."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of Information Systems", "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 Planning?"}, {"role": "assistant", "content": "According to Technical Guide to Information Security Testing and Assessment:\n\n| 4.4 | Wireless Scanning | ...................................................................................................4-6 | | | 4.4.1 Passive Wireless Scanning ..........................................................................4-8 | | | | 4.4.2 Active Wireless Scanning.............................................................................4-9 | | | | 4.4.3 Wireless Device Location Tracking | ..............................................................4-9 | | | 4.4.4 Bluetooth Scanning ....................................................................................4-10 | | | 4.5 | Summary................................................................................................................4-10 | | | Target Vulnerability Validation Techniques | ..................................................................5-1 | | | 5.1 | Password Cracking..................................................................................................5-1 | | | 5.2 | Penetration Testing..................................................................................................5-2 | | | | 5.2.1 Penetration Testing Phases | .........................................................................5-2 | | | 5.2.2 Penetration Testing Logistics | .......................................................................5-5 | | 5.3 | Social Engineering...................................................................................................5-6 | | | 5.4 | Summary..................................................................................................................5-7 | | | Security Assessment | Planning.......................................................................................6-1 | | | 6.1 | Developing a Security Assessment Policy...............................................................6-1 | | | 6.2 | Prioritizing and Scheduling Assessments................................................................6-1 | | | 6.3 | Selecting and Customizing Techniques...................................................................6-3 | |"}], "metadata": {"source": "Technical Guide to Information Security Testing and Assessment", "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 Guide to Computer Security Log Management:\n\napplications such as supply chain management, financial management, procurement systems, enterprise resource planning, and customer relationship management. In addition to COTS and GOTS software, most organizations also use custom-developed applications tailored to their specific requirements. 8"}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Zero Trust Architecture provide? (Part 2)"}, {"role": "assistant", "content": "as normas y directrices no se aplicarán a los sistemas de seguridad nacional sin la aprobación expresa de los funcionarios federales apropiados que ejercen la autoridad política sobre dichos sistemas.\nEsta directriz es coherente con los requisitos de la Circular A-130 de la Oficina de Gestión y Presupuesto (OMB). Nada de lo que figura en esta publicación debe interpretarse como contradictorio con las normas y directrices que el Secretario de Comercio ha hecho obligatorias y vinculantes para los organismos federales en virtud de la autoridad legal. Estas directrices tampoco deben interpretarse como una alteración o sustitución de las autoridades existentes del Secretario de Comercio, el Director de la OMB o cualquier otro funcionario federal. Esta publicación puede ser utilizada por organizaciones no gubernamentales de forma voluntaria y no está sujeta a derechos de autor en los Estados Unidos. No obstante, el NIST agradecerá que se cite su procedencia. Publicación especial 800-207 del Instituto Nacional de Estándares y Tecnología (NIST)\n\nInst. Nac. Est. Technol. Publ. Espec. 800-207, 59 páginas (agosto de 2020) CODEN: NSPUE2\n\nEsta publicación está disponible en inglés de forma gratuita en: https://doi.org/10.6028/NIST.SP.800-207\n\nEn este documento pueden identificarse ciertas entidades, equipos o materiales comerciales con el fin de describir adecuadamente un procedimiento o concepto experimental. Dicha identificación no implica una recomendación o aprobación por parte del NIST, ni que las entidades, materiales o equipos sean necesariamente los mejores disponibles para el propósito. En esta publicación puede haber referencias a otras que actualmente están siendo desarrolladas por NIST de acuerdo con sus responsabilidades estatutarias asignadas."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities:\n\n\\_i.ligaga/t\\_i.ligaon; labeled dataset; genera/t\\_i.ligaon tool; graph genera/t\\_i.ligaon; AI models; formal methods; CVE; CWE; NVD; KEV. | 2. | Current State of the Art . | . . . . . . . . . . . . .\n| 3 |\n|------|-----------------------------------------|-----------------------------------------------------------------------------|-----|\n| 3. | Bugs Framework Formalism . . . . . | . . . . . . . . . . . . | 5 |\n| | 3.1. | BF Opera/t_i.ligaon . . . . . . . . . . . . | 7 |\n| | 3.2. | BF Bug, Fault, and Weakness . . . . . . . . . . . . . . . . | 8 |\n| | 3.3. | BF Vulnerability . . . . . . . . | 10 |\n| | 3.4. | BF Bug Iden/t_i.liga/uniFB01ca/t_i.ligaon . . . . . . . . . . . . . . . . | 13 |\n| 4. | BF Security Concepts . . | . . . . . . . . . . . . . | 14 |\n| 5. | BF Bugs Models . | . . . . . . . . . . . . . . . . | 16 |\n| | 5.1. | BF Input/Output Check ( INP) Bugs Model . . . . . . | 16 |\n| | 5.2. | BF Memory ( MEM) Bugs Model | 17 |\n| | 5.3. | BF Data Type ( DAT) Bugs Model . . . . . . . . . | 18 |\n| 6. | BF Taxonomy . . . . . . . . . . . . . . | . . . . . . . | 20 |\n| | 6.1. | BF Weakness Classes . . . . . . . . . . . . . | 20 |\n| | 6.2. | BF Failure Class . . . . . . . . . . . . . | 26 |\n| | 6.3. | BF Methodology . . . . . . . . . . . . . . . | 26 |\n| 7. | BF Vulnerability Models | . . . . . . . . . . . . . . | 29 |\n| | 7.1. | BF Vulnerability State Model . . . . . . . . | 29 |\n| | 7.2. | BF Vulnerability Speci/uniFB01ca/t_i.ligaon Model . . . . . . . . . . . . . | 35 |\n| 8. | BF Formal Language . . . . . . | . . . . . . | 39 |\n| | 8.1. | BF Lexis . . . . . . . . . . . . . . . | 40 |\n| | 8.2. | BF Syntax . . . . . . . . . . . . . . . . . . . | 42 |\n| | 8.3. | BF Seman/t_i.ligacs . . . . . . . . . . . . . . . . . | 44 |\n| 9. | BF Secure Coding Principles | . . . . . . . . . . . ."}], "metadata": {"source": "Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Secure Domain Name System (DNS) Deployment Guide:\n\nChecklist Item 27: If the zone is signed using NSEC3 RRs, the iterations value should be based on available computing power available to clients and attackers. The value should be reviewed annually and increased if the evaluation conditions change. Initial values should be between 1 and 200 iterations when using SHA-1 and 1 and 100 if using SHA-256.\n\n- Checklist item 26: If the zone is signed using NSEC3 RRs, the salt value should be changed every time the zone is completely resigned. The value of the salt should be random, and the length should be short enough to prevent a FQDN to be too long for the DNS protocol (i.e. under 256 octets).\n- Checklist item 27: If the zone is signed using NSEC3 RRs, the iterations value should be based on available computing power available to clients and attackers. The value should be reviewed annually and increased if the evaluation conditions change.\n- Checklist item 28: TTL values for DNS data should be set between 30 minutes (1800 seconds) and 24 hours (86400 seconds).\n- Checklist item 29 : TTL values for RRsets should be set to be a fraction of the DNSSEC signature validity period of the RRSIG that covers the RRset."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment Guide", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Engineering Trustworthy Secure Systems:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | F.2. | Assurance..............................................................................................................104 | Assurance..............................................................................................................104 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| Appendix G. | Appendix G. | Life Cycle Processes Overview..............................................110 |\n| G.1. Process Overview..................................................................................................110 | G.1."}], "metadata": {"source": "Engineering Trustworthy Secure 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 Services Acquisition?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nOrganizations are concerned about the risks associated with products and services that may potentially contain malicious functionality, are counterfeit, or are vulnerable due to poor manufacturing and development practices within the supply chain. These risks are associated with an enterprise's decreased visibility into and understanding of how the technology they acquire is developed, integrated, and deployed or the processes, procedures, standards, and practices used to ensure the security, resilience, reliability, safety, integrity, and quality of the products and services.\n\nThis publication provides guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain at all levels of their organizations. The publication integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach, including guidance on the development of C-SCRM strategy implementation plans, C-SCRM policies, C-SCRM plans, and risk assessments for products and services."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Digital Identity Guidelines_ Authentication and Authenticator Management provide?"}, {"role": "assistant", "content": "NIST Special Publication\nNIST SP 800-63B-4\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nDavid Temoshok\nJames L. Fenton\nYee-Yin Choong\nNaomi Lefkovitz\nAndrew Regenscheid\nRyan Galluzzo\nJustin P. Richer\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63B-4\n\n\fNIST Special Publication\nNIST SP 800-63B-4\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nDavid Temoshok\nNaomi Lefkovitz *\nRyan Galluzzo\nApplied Cybersecurity Division\nInformation Technology Laboratory\n\nYee-Yin Choong\nInformation Access Division\nInformation Technology Laboratory\n\nAndrew Regenscheid\nComputer Security Division\nInformation Technology Laboratory\n\nJames L. Fenton\nAltmode Networks\n\nJustin P. Richer\nBespoke Engineering\n\n* Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-63B-4\n\nJuly 2025\n\nNational Institute of Standards and Technology\nCraig Burkhardt, Acting Under Secretary for Standards and Technology and Acting NIST Director\n\nU.S. Department of Commerce\nHoward Lutnick, Secretary\n\n\fCertain equipment, instruments, software, or materials, commercial or non-commercial,\nare identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product\nor service by NIST, nor does it imply that the materials or equipment identified are\nnecessarily the best available for the purpose. There may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-38F December 2012\n\n\n\n## Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping\n\nMorris Dworkin\n\n## C O M P U T E R S E C U R I T Y\n\nNIST Special Publication 800-38F\n\n## Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping\n\nMorris Dworkin\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899\n\nDecember 2012\n\n\n\n## U.S. Department of Commerce\n\nRebecca M. Blank, Acting Secretary\n\nNational Institute of Standards and Technology Patrick D. Gallagher, Director\n\n## NIST Special Publication 800-38F\n\n## Reports on Information Security 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 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. Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Methods for Key Wrapping", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Configuration Management?"}, {"role": "assistant", "content": "According to Fiscal Year 2024 Cybersecurity and Privacy Annual Report:\n\ned the IoT Interagency Federal Working Group and collaborated with the IoT Advisory Board as it developed findings and recommendations on how the U.S. can reduce barriers to adopting IoT technologies.\nThe findings were documented in a September 2024 report."}], "metadata": {"source": "Fiscal Year 2024 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - Illustrative diagram, schematic, or photograph of the module. A photograph included for hardware modules. If the security policy encompasses multiple versions of the module, each version is represented separately or annotated that the representation is illustrated for all versions. For a software or , firmware, hybrid, or sub-chip cryptographic module, the security policy includes a block diagram that illustrates:\n- o The location of the logical object of the software or firmware module with respect to the operating system, other supporting applications, and the cryptographic boundary so that all of the logical and physical layers between the logical object and the cryptographic boundary are clearly defined and\n- o The interactions of the logical object of the software or firmware module with the operating system and other supporting applications resident within the cryptographic boundary."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Managing the Security of Information Exchanges:\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\nInformation exchange occurs via communications technology usually provided by an internet service provider (ISP) or via a system interconnection (physical or virtual), which may itself employ the services of an ISP or telecommunications vendor. Methods to exchange information and for which some type of information exchange agreement 4 may be warranted include but are not limited to direct exchange (including access) across a system interconnection, electronic or digital file transfers, file-sharing services, database access/sharing or exchanges of database transaction information, exchange of information via portable storage device (which does not use an ISP or system interconnection), and email exchange.\n\nThe dedicated or on-demand circuit or the VPN is the 'pipe' that connects the systems. Employment of a dedicated circuit may be more expensive, but it provides greater security assurance for the information exchange because the circuit may only be breached through a direct physical intrusion."}], "metadata": {"source": "Managing the Security of Information Exchanges", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.3.1."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "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 Media Protection?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nSemiconductor-based hardware is the foundation of modern-day electronics - from smartphones, computers, and telecommunications to transportation and critical infrastructure. The semiconductor hardware supply chain is a complex network of companies that collectively provide intellectual property, designs, and raw materials and manufacture, test, package, and distribute products. Coordination among the components of a supply chain is required at different stages, including inception, deployment to end users, maintenance during use, and disposal or end of life. Securing semiconductor-based hardware and their supply chains help protect sensitive information, maintain the integrity of systems, and ensure overall stability across the infrastructure and connected world."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Managing the Security of Information Exchanges:\n\nManaging the Security of Information Exchanges provides guidance for planning, establishing, maintaining, and discontinuing information exchange and access between systems that are owned and operated by different organizations (internal or external) or that cross authorization boundaries. The guidance is consistent with the requirements specified in the Office of Management and Budget (OMB) Circular A-130 for the secure management of information exchanges. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | Introduction....................................................................................................................."}], "metadata": {"source": "Managing the Security of Information Exchanges", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\n\n3.2.4."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines on Electronic Mail Security:\n\n- GLYPH<c=31,font=/HABHKN+Webdings> Types of personnel required (e.g., system and mail server administrators, network administrators, information systems security officers)\n- GLYPH<c=31,font=/HABHKN+Webdings> Skills and training required by assigned personnel\n- GLYPH<c=31,font=/HABHKN+Webdings> Availability of personnel.\n\n- GLYPH<c=31,font=/HABHKN+Webdings> Coordinating the development and maintenance of the organization's information security policies, standards, and procedures\n- GLYPH<c=31,font=/HABHKN+Webdings> Coordinating the development and maintenance of the organization's change control and management procedures\n- GLYPH<c=31,font=/HABHKN+Webdings> Ensuring the establishment of, and compliance with, consistent IT security policies for departments throughout the organization\n- GLYPH<c=31,font=/HABHKN+Webdings> Coordinating with upper management, public affairs, and other relevant personnel to produce a formal policy and process for email usage guidelines (e.g., personal use, monitoring, encryption).\n\nThe greatest challenge and expense in developing and securely maintaining a mail server is providing the necessary human resources to adequately perform the required functions. Many organizations fail to fully realize the amount of expense and skills required to field a secure mail server. This failure often results in overworked employees and insecure systems. From the initial planning stages, organizations need to determine the necessary human resource requirements. Appropriate and sufficient human resources are the single most important aspect of mail server security. Organizations should also consider the fact that, in general, technical solutions are not a substitute for skilled and experienced personnel."}], "metadata": {"source": "Guidelines on Electronic Mail Security", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to System and Network Security Acronyms and Abbreviations:\n\nds of electromagnetic radiation to personnel |\n| HF | high frequency |\n| HFS | Hierarchical File System |\n| HHS | U.S.\nDepartment of Health and Human Services |\n| HINFO | host information |\n| HIP | Host Identity Protocol |\n| HIPAA | Health Insurance Portability and Accountability Act |\n| HIPERLAN | high-performance radio local area network |\n| HKLM | HKEY_Local_Machine |\n| HL7 | Health Level Seven |\n| HMAC | keyed-hash message authentication code |\n| HMI | human-machine interface |\n| HPA | host protected area |\n| HPFS | High-Performance File System |\n| HR | human resources |\n| HSARPA | Homeland Security Advanced Research Projects Agency |\n| HSPD | Homeland Security Presidential Directive |\n| HTCIA | High Technology Crime Investigation Association |\n| HTCP | Hyper Text Caching Protocol |\n| HTML | Hypertext Markup Language |\n| HTTP | Hypertext Transfer Protocol |\n| HTTPS | Secure Hypertext Transfer Protocol |\n| Hz | hertz |"}], "metadata": {"source": "System and Network Security Acronyms and Abbreviations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3:\n\n- Content authors and editors seeking to ensure that the SCAP source content they produce operates correctly, consistently, and reliably in SCAP products.\n- Software developers and system integrators seeking to create, use, or exchange SCAP content in their products or service offerings.\n- Product developers preparing for SCAP validation at an accredited independent testing laboratory.\n\n1. For each <xccdf:check-content-ref> element, a content consumer either SHALL attempt to retrieve the document referenced by the <ds:component-ref> element that is referenced directly by the <xccdf:check-content-ref> element's @href attribute, or it SHALL resolve the @href attribute within the context of the XML Catalog specified as part of the <ds:component-ref> element used to reference this benchmark. If not resolvable, the next available <xccdf:check-content-ref> element SHALL be evaluated. If none of the <xccdf:check-content-ref> elements are resolvable, then the result of the rule evaluation SHALL be the XCCDF 'notchecked' status and processing of the check SHALL end.\n2. Once a resolvable <xccdf:check-content-ref> element is found, then checking system processing SHALL proceed. When evaluating a rule, an < xccdf:ruleresult/xccdf:message > with the @severity attribute value of 'info' SHALL be generated, indicating the < xccdf:check-content-ref > @href attribute and @name attribute, if provided.\n\nAn SCAP result data stream contains the results of the evaluation of one or more SCAP source data streams by an SCAP content consumer. The following requirements and recommendations pertain to content consumers generating SCAP result data streams."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program:\n\nOrganizational, financial, and regulatory reasons drive the desire to build a robust information security measurement program. Such programs facilitate decision-making and improve performance and accountability by providing a structure for collecting, analyzing, and reporting relevant and related data. Organizations can use measures as management tools in their internal improvement efforts and link the implementation of their information security programs to agency- and enterprise-level planning efforts. An information security measurement program can increase accountability by helping organizations identify if specific controls that are implemented correctly, are not implemented, or are ineffective. The continuous feedback provided by a structured measurement program supports regular internal communications that collect data about information security performance and risks for high-level members of the organization. Implementing an information security measurement program demonstrates an organizational commitment to proactive information security and continuous improvement. For example, organizations that use the Cybersecurity Capacity Maturity Model (CMM) may implement a measurement program as part of the goal of demonstrating the Level 4, 'Managed,' degree of performance. When using the appropriate measures, an information security measurement program enables organizations to quantify improvements in securing systems and demonstrate quantifiable progress in accomplishing strategic goals and objectives. More information on selecting measures can be found in SP 800-55v1. This section outlines the key roles and responsibilities for developing and implementing an information security measurement program. While all organization members are ultimately responsible for information security, the positions described here are specific to key information security stakeholders."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to U.S. Department of Energy Risk Assessment Methodology:\n\nents (BLSRs) set forth in all applicable DOE Orders. The Baseline Security Requirements as used in this guideline encompass DOE Orders 1360. 2A, 5637.1, and all relevant guidelines, orders, laws, etc.\nIn the previous step you identified whether your system was involved in sensitive unclassified or classified processing. In this step, you are asked to review brief lists of security countermeasures (baseline security requirements) that MUST be in place, per the applicable DOE orders"}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3:\n\n- Languages. The SCAP languages provide standard vocabularies and conventions for expressing security policy, technical check mechanisms, and assessment results. The SCAP language specifications are Extensible Configuration Checklist Description Format (XCCDF), Open Vulnerability and Assessment Language (OVAL), and Open Checklist Interactive Language (OCIL). - Reporting formats. The SCAP reporting formats provide the necessary constructs to express collected information in standardized formats. The SCAP reporting format specifications are Asset Reporting Format (ARF) and Asset Identification. Although Asset Identification is not explicitly a reporting format, SCAP uses it as a key component in identifying the assets that reports relate to. - Identification schemes. The SCAP identification schemes provide a means to identify key concepts such as software products, vulnerabilities, and configuration items using standardized identifier formats. They also provide a means to associate individual identifiers with additional data pertaining to the subject of the identifier. The SCAP identification scheme specifications are Common Platform Enumeration (CPE), Software Identification (SWID) Tags, Common Configuration Enumeration (CCE), and Common Vulnerabilities and Exposures (CVE). - Measurement and scoring systems. In SCAP this refers to evaluating specific characteristics of a security weakness (for example, software vulnerabilities and security configuration issues) and, based on those characteristics, generating a score that reflects their relative severity. The SCAP measurement and scoring system specifications are Common Vulnerability Scoring System (CVSS) and Common Configuration Scoring System (CCSS). - Integrity. An SCAP integrity specification helps to preserve the integrity of SCAP content and results. Trust Model for Security Automation Data (TMSAD) is the SCAP integrity specification."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThis publication provides guidance to organizations on identifying, assessing, and mitigating cybersecurity risks throughout the supply chain at all levels of their organizations. The publication integrates cybersecurity supply chain risk management (C-SCRM) into risk management activities by applying a multilevel, C-SCRM-specific approach, including guidance on the development of C-SCRM strategy implementation plans, C-SCRM policies, C-SCRM plans, and risk assessments for products and services. acquire; C-SCRM; cybersecurity supply chain; cybersecurity supply chain risk management; information and communication technology; risk management; supplier; supply chain; supply chain risk assessment; supply chain assurance; supply chain risk; supply chain security. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls..............................................................................................."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Computer Security Division 2007 Annual Report:\n\n53 | | Computer Security Division Publications - FY 2007 | 54 | | Ways to Engage Our Division and NIST | 56 |"}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "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 Automated Information System Security Accreditation Guidelines provide? (Part 4)"}, {"role": "assistant", "content": "| 8. | SUMMARY | 33 |\n| 9. ACCREDITATION TRANSMITTAL | 9. ACCREDITATION TRANSMITTAL | 9.\nACCREDITATION TRANSMITTAL | 3 5 |\n| ACCREDITATION ACTION | ACCREDITATION ACTION | ACCREDITATION ACTION | |\n| APPENDIX | APPENDIX | APPENDIX | i |\n| AISSM | AISSM | AISSM | i |\n| | AISSC | AISSC | i |\n| THE DAA ii FORMS | THE DAA ii FORMS | THE DAA ii FORMS | THE DAA ii FORMS |\n| 1. DPA Security Profile | 1. DPA Security Profile | 1. DPA Security Profile | 13 |\n| 2. Office Automation DPA Risk Assessment | 2. Office Automation DPA Risk Assessment | 2. Office Automation DPA Risk Assessment | 19 |\n| 3. Contingency Plan Waiver | 3. Contingency Plan Waiver | 3. Contingency Plan Waiver | 31 |\n| 4. Sensitive Application Security | 4. Sensitive Application Security | Certification Waiver | 34 |\n| 5. Accreditation Request | 5. Accreditation Request | 5. Accreditation Request | 37 |\n| 6. Accreditation Statement | 6."}], "metadata": {"source": "Automated Information System Security Accreditation Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\naccess control; confidentiality; cryptographic key management system; disaster recovery; federal cryptographic key management system; integrity; metadata; security assessment; security functions; security policies; source authentication. | | 6.7.2 Restricting Cryptographic Module Entry and Output of Plaintext | Keys............................................................................................65 |\n|---------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|\n| | 6.7.3 Controlling Human Input.....................................................................65 | |\n| | 6.7.4 Multiparty Control | ...............................................................................66 |\n| | 6.7.5 Key Splitting | .......................................................................................66 |\n| 6.8 | Compromise Recovery ................................................................................."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to A Review of U.S. and European Security Evaluation Criteria:\n\n* Division D; Minimal Protection -This division contains only one class. It is reserved for those systems that have been evaluated but that fail to meet the requirements for a higher evaluation class.\n* Division C: Discretionary Protection -Classes in this division provide discretionary (need-to-know) protection and, through the inclusion of audit capabilities, accountability of subjects and the actions they initiate.\n* Division B; Mandatory Protection -The concept of a security relevant or Trusted Computing Base (TCB) that preserves the integrity of sensitivity labels and uses them to enforce a set of mandatory access control rules\n\nPart II describes a number of additional security services (e.g., communications integrity, denial of service, transmissions security) that arise in conjunction with networks. The full range of physical and administrative security measures appropriate to the highest sensitivity level of information on the network must be in place in order to operate a trusted network as described in the Red Book\n\nThe term integrity as used in the Red Book requires some explanation. In Part I integrity refers to the correct operation of the network trusted computer base hardware/ firmware , and protection against unauthorized modification of labels and data. Division A and B networks must protect the labels that represent the sensitivity of information and the corresponding authorizations of users."}], "metadata": {"source": "A Review of U.S. and European Security Evaluation Criteria", "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Computer Security Division 2013 Annual Report:\n\ninistration (GSA), Bureau of the Fiscal Service, and NIST. Recent administration guidance directing federal agencies to reduce travel and conference budgets significantly reduced attendance.\nTechnical sessions included briefings on evolving cybersecurity strategies, IT security concerns during a consolidation (merger), supply chain risk management activities, the National Vulnerability Database (NVD), SP 800-53 Revision 4, continuous monitoring, industrial control systems security, and EO 13636."}], "metadata": {"source": "Computer Security Division 2013 Annual Report", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\nIndividuals responsible for developing and leading cybersecurity programs are the primary audience for the CSF. The CSF can also be used by others involved in managing risk - including executives, boards of directors, acquisition professionals, technology professionals, risk managers, lawyers, human resources specialists, and cybersecurity and risk management auditors - to guide their cybersecurity-related decisions. Additionally, the CSF can be useful to those making and influencing policy (e.g., associations, professional organizations, regulators) who set and communicate priorities for cybersecurity risk management. The CSF is the result of a multi-year collaborative effort across industry, academia, and government in the United States and around the world. NIST acknowledges and thanks all of those who have contributed to this revised CSF. Information on the CSF development process can be found on the NIST CSF website. Lessons learned about the use of the CSF can always be shared with NIST at cyberframework@nist.gov. - on C-SCRM. SP 800-161r1 (Revision 1), Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations , provides in-depth information on C-SCRM. - Risks from emerging technologies: As new technologies and new applications of technology become available, new risks become clear. A contemporary example is artificial intelligence (AI), which has cybersecurity and privacy risks, as well as many other types of risk. The NIST Artificial Intelligence Risk Management Framework (AI RMF) was developed to help address these risks. Treating AI risks alongside other enterprise risks (e.g., financial, cybersecurity, reputational, and privacy) will yield a more integrated outcome and organizational efficiencies. Cybersecurity and privacy risk management considerations and approaches are applicable to the design, development, deployment, evaluation, and use of AI systems."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 | CHAPTERONE INTRODUCTION...................................................................................................... 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSEANDAPPLICABILITY ..................................................................................................."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions:\n\nFor hash functions, the input is called the message , and the output is called the (message) digest or the hash value . The length of the message can vary; the length of the digest is fixed. A cryptographic hash function is a hash function that is designed to provide special properties, including collision resistance and preimage resistance, that are important for many applications in information security. For example, a cryptographic hash function increases the security and efficiency of a digital signature scheme when the digest is digitally signed instead of the message itself. In this context, the collision resistance of the hash function provides assurance that the original message could not have been altered to a different message with the same hash value, and hence, the same signature. Other applications of cryptographic hash functions include pseudorandom bit generation, message authentication codes, and key derivation functions. The KECCAKp permutations were designed to be suitable as the main components for a variety of cryptographic functions, including keyed functions for authentication and/or encryption. The six SHA-3 functions can be considered as modes of operation (modes) of the KECCAKp [1600,24] permutation. In the future, additional modes of this permutation or other KECCAKp permutations may be specified and approved in FIPS publications or in NIST Special Publications. | hash value | See digest. |\n|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| HMAC | Keyed-Hash Message Authentication Code. |\n| KDF | Key derivation function. |\n| KECCAK | The family of all sponge functions with a KECCAK- f permutation as the underlying function and multi-rate padding as the padding rule."}], "metadata": {"source": "SHA-3 Standard_ Permutation-Based 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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity” provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, 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\nMegas KN, Fagan M, Cuthill B, Hoehn B, Lemire D, Herold R (2022) Workshop Summary Report for 'Building on the NIST Foundations: Next Steps in IoT Cybersecurity'. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8431. https://doi.org/10.6028/NIST.IR.8431\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448\n\nMichael Fagan: 0000-0002-1861-2609\n\nBarbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\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."}], "metadata": {"source": "Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Security and Trust Considerations for Digital Twin Technology:\n\n- Unmanned aerial vehicles (drones): Unmanned aerial vehicles (UAVs) or drones are used in environmental monitoring. UAVs come in all sizes, shapes, configurations, and levels of sophistication. More advanced drones can operate autonomously or under the control of a human in a command-and-control center that is far from the UAV's physical location. Remote operators of UAVs have user interfaces that provide the real-time information about the UAV's state and condition.\n- Ocean-going vessels: Digital twins can be used to construct 2D and 3D static views or VR/AR views of ocean vessels. VR/AR views would enable architects, designers, engineers, and maintenance crews to see the vessel as if they were physically walking through it. During operations, digital twin technology would enable operators and crew members to monitor every aspect of the ship, possibly precluding the need for certain physical monitoring and inspections.\n- Oil derricks and ocean-drilling platforms: Oil derricks may drill for oil in inhospitable and potentially treacherous environments at great depths. Systems built around digital twins enable designers, engineers, and operators to form models and visual representations of oil rigs, drill rigs, and drill bit heads deep in the ocean.\n- Robotic surgery: There are surgical robots that perform various kinds of surgery. Some require an actual human surgeon to control the robot, while others only require a human surgeon to monitor the robot's automatic execution of the surgery. Digital twin technology could be used in pre-surgery planning and to foster surgical tool interoperability. For example, one company's surgical robot could interoperate with another company's VR system that specializes in the representation of human organs."}], "metadata": {"source": "Security and Trust Considerations for Digital Twin Technology", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Random Bit Generator (RBG) Constructions:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The NIST Special Publication (SP) 800-90 series of documents supports the generation of highquality random bits for cryptographic and non-cryptographic use. SP 800-90A, Recommendation for Random Number Generation Using Deterministic Random Bit Generators , specifies several deterministic random bit generator (DRBG) mechanisms based on cryptographic algorithms. SP 800-90B, Recommendation for the Entropy Sources Used for Random Bit Generation , provides guidelines for the development and validation of entropy sources. This document (SP 800-90C) specifies constructions for the implementation of random bit generators (RBGs) that include DRBG mechanisms as specified in SP 800-90A and that use entropy sources as specified in SP 80090B. Constructions for four classes of RBGs - namely, RBG1, RBG2, RBG3, and RBGC - are specified in this document. 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."}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to A Threat Analysis on UOCAVA Voting Systems:\n\n| X | | LEAST PRIVILEGE | Databases and IT systems used to manage registration information should be protected with access control mechanisms.\n|\n| IA-1 | X | | X | IDENTIFICATION AND AUTHENTICATION POLICY AND PROCEDURES | Officials should develop procedures and implement technical mechanisms to identify voters, election officials and system administrators. Procedures may be used to authenticate voters, while IT systems should include IA and access control mechanisms. |\n| IA-2 | X | | X | USER IDENTIFICATION AND AUTHENTICATION | Officials should develop procedures and implement technical mechanisms to identify voters, election officials and system administrators. Procedures may be used to authenticate voters, while IT systems should include IA and access control mechanisms. |\n| IA-4 | X | | X | IDENTIFIERMANAGEMENT | Officials should develop procedures and implement technical mechanisms to identify voters, election officials and system administrators. Procedures may be used to authenticate voters, while IT systems should include IA and access control mechanisms. |\n| IA-5 | X | | X | AUTHENTICATORMANAGEMENT | Officials should develop procedures and implement technical mechanisms to identify voters, election officials and system administrators. Procedures may be used to authenticate voters, while IT systems should include IA and access control mechanisms. |\n| IR-4 | | X | X | INCIDENT HANDLING | Officials should monitor for disruptions in their IT systems and in external essential systems, such as postal mail delivery."}], "metadata": {"source": "A Threat Analysis on UOCAVA Voting 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 additional guidance does Guide to Malware Incident Prevention and Handling for Desktops and Laptops provide? (Part 4)"}, {"role": "assistant", "content": "e and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures.\nIt also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones. ## Keywords\n\nincident response; information security; malware\n\n## Acknowledgments\n\nThe authors, Murugiah Souppaya of the National Institute of Standards and Technology (NIST) and Karen Scarfone of Scarfone Cybersecurity, thank their colleagues who assisted with developing this revision of the publication. ## Acknowledgments, Original Version of SP 800-83\n\nThe authors, Peter Mell of the National Institute of Standards and Technology (NIST) and Karen Kent and Joseph Nusbaum of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. The authors would particularly like to acknowledge Tim Grance and Murugiah Souppaya of NIST and Lucinda Gagliano, Thomas Goff, and Pius Uzamere of Booz Allen Hamilton for their keen and insightful assistance throughout the development of the document. The authors would also like to express their thanks to security experts Mike Danseglio (Microsoft), Kurt Dillard (Microsoft), Michael Gerdes (Getronics RedSiren Security Solutions), Peter Szor (Symantec), Miles Tracy (U.S. Federal Reserve System), and Lenny Zeltser (Gemini Systems LLC), as well as representatives from the General Accounting Office, and for their particularly valuable comments and suggestions. The National Institute of Standards and Technology would also like to express its appreciation and thanks to the Department of Homeland Security for its sponsorship and support of NIST Special Publication 80083."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 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 additional guidance does Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-05-15\n\n## How to Cite this NIST Technical Series Publication\n\nFagan M, Gilbert D (2025) Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8557. https://doi.org/10.6028/NIST.IR.8557\n\n## Author ORCID iDs\n\nMichael Fagan: 0000-0002-1861-2609\n\nDylan Gilbert: 0009-0003-6061-3757\n\n## Contact Information\n\nimmersivetech@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8557/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis document reports on the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies (the Workshop) hosted by the Symposium in Usable Privacy and Security (SOUPS). The Workshop was held on August 7 th , 2024 before the in-person symposium held August 11 th and 12 th , 2024 in Philadelphia, Pennsylvania."}], "metadata": {"source": "Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Mobile Forensic Reference Materials_ a Methodology and Reification:\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 Interagency Report discusses ITL's research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations.\n\nThe results from past and recent work indicate that assessments of mobile forensic tools can reveal subtle inaccuracies that exist. While the approach discussed in this report is suited for identity modules, it is not immediately clear whether the same or a similar approach could be used to populate handsets and how that might be realized. Figure 13 shows one possibility. The adaption is to use agent applications that are platform dependent, coded in a suitable language, and executed directly on the handset. Many platform families allow middleware development and support a common Application Programming Interface (API) suitable for this purpose. The application and data could be brought to the handset through various means, such as a memory card or data transfer, and the same means used to retrieve the summary report."}], "metadata": {"source": "Mobile Forensic Reference Materials_ a Methodology and Reification", "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 Guide for Security-Focused Configuration Management of Information Systems:\n\n| Date | Type | Change | Page | |------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------| | 10/10/2019 | Substantive | Appendix F, section 3: Changed from: 'NIST SP 800-46: Guide to Enterprise Telework and Remote Access Security;' to 'NIST [SP 800-46]: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security' 'NIST SP 800-52: Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations' to 'NIST [SP 800-52]: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations;' and 'NIST SP 800-124: Guidelines on Cell Phone and PDA Security' to 'NIST [SP 800- 124]: Guidelines for Managing the Security of Mobile Devices in the Enterprise' | F-1 - F-2 | | 10/10/2019 | Substantive | Appendix F, section 4: Added 'Associated NIST [SP 800-53] Control: CM-7.' | F-2 | | 10/10/2019 | Substantive | Appendix F, section 5: Added 'Associated NIST [SP 800-53] Control: AC-17.' | F-2 | | 10/10/2019 | Substantive | Appendix F, section 5: Changed from: 'NIST SP 800-46: Guide to Enterprise Telework and Remote Access Security;' to 'NIST [SP 800-46]: Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security' 'NIST SP 800-52: Guidelines for the Selection and Use of"}], "metadata": {"source": "Guide for Security-Focused Configuration Management of Information Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI:\n\n3.2.4 POSIX 1\n\nConformance Document, October 1994\nGTI - Supported by Product\nMFS - Supported by Product\n\nMC - Not Provided by Product\nAP - Supported by Product\n\nComputer Hardware Supplier: American Megatrends, Inc. 3.2.4 POSIX 1\n\nConformance Document, October 1994\nGTI - Supported by Product\nMFS - Supported by Product\n\nMC - Not Provided by Product\nAP - Supported by Product\n\nComputer Hardware Supplier: Compaq Computer Corporation\nComputer Hardware Product: Compaq Proliant 2000, Model 5/66\nC Compiler: SCO ODT Development System Release 3. 3.2.4 POSIX 1 Conformance\n\nDocument, October 1994\n\nGTI - Supported by Product\nMFS - Supported by Product\n\nMC - Not Provided by Product\nAP - Supported by Product\n\nComputer Hardware Supplier: Compaq Computer Corporation\nComputer Hardware Product: Compaq ProLiant 2000, Model 5/90\nC Compiler: SCO ODT Development System Release 3."}], "metadata": {"source": "Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Networks of 'Things':\n\n2 RFID is an automatic identification method that stores and remotely retrieves data via a RFID tag or transponder. A RFID programmer encodes information onto a tiny microchip within a thin RFID inlay. In supply chain applications, these inlays typically are embedded in a tag that looks similar to pressure sensitive labels. RFID inlays can be applied to a wide variety of NoTs. RFID technology offers security and reliability features that enhance trustworthiness in IoT ecosystems."}], "metadata": {"source": "Networks of 'Things'", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does U.S. Department of Energy Risk Assessment Methodology provide? (Part 4)"}, {"role": "assistant", "content": "| | 34 | |\n| STEP | | | |\n| 4 REVIEW ANY | | 37 | |\n| | .\n| | |\n| | R4 | | |\n| | | 41 | |\n| | | | R4 |\n\n## TABLE OF CONTENTS (Continued)\n\n| | | | Page Number | |\n|------|--------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|----|\n| | R4 . | Sample Impacts of Threats to and Vulnerabilities of Communications | Sample Impacts of Threats to and Vulnerabilities of Communications | 44 |\n| | R4.5a | Sample Impacts of Threats to and Vulnerabilities of Computer Hardware | Sample Impacts of Threats to and Vulnerabilities of Computer Hardware | 45 |\n| | R4.5b | Sample Impacts of Threats to and Vulnerabilities of Computer Software | Sample Impacts of Threats to and Vulnerabilities of Computer Software | 46 |\n| | R4 ."}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 IR.L2-3.6.2 (NIST 3.6.2)?"}, {"role": "assistant", "content": "According to Module-Lattice-Based Digital Signature Standard:\n\n3.6.2 | Public-Key and Signature Length Checks | 12 |\n| | | 3. 3.6.2 Public-Key and Signature Length Checks\n\nAlgorithm 3, implementing verification for ML-DSA, and Algorithm 5, implementing verification for HashMLDSA, specify the length of the signature 𝜎 and the public key 𝑝𝑘 in terms of the parameters described in Table 1."}], "metadata": {"source": "Module-Lattice-Based Digital Signature Standard", "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 Computer Security Bulletin Board System_ User's Guide provide? (Part 5)"}, {"role": "assistant", "content": "ilable to federal agencies and to the public a wide variety of computer security information and encourages the sharing of information which can help users and managers protect their data and systems.\nInformation posted on the BBS include an events calendar, software reviews, publications, bibliographies, lists of organizations, and other government bulletin board numbers. This BBS contains no sensitive unclassified or classified information. ## 1.2. Bulletin Board Access and Structure\n\nThe Computer Security BBS operates twenty-four hours a day, charges no fee, and is accessible to anyone who has a computer or terminal with either a modem or Internet connection. The BBS requires callers to enter a name and a password, a process called \"logging on.\" All BBS users have equal access to the posted information, and may use the BBS for a maximum of sixty minutes per call and seventy minutes per day. A user who is finished using the BBS disconnects from it, a process called \"logging off.\" The BBS automatically logs off any inactive user, i.e., one who does not press at least one key for a period of three minutes. There will be a warning bell and an on-screen message before automatic log off. If your account is unused after a period of six months, your account is deleted. The bulletin board system contains three subsystems. The bulletin subsystem consists of topic menus with numerous bulletins listed under each topic. Each bulletin contains a limited amount of information, normally consisting of one to three pages. The bulletins can be viewed on the computer screen or can be downloaded (i.e., transferring the entire file to the user's system) for future reference. The file subsystem consists of larger amounts of information that can only be viewed by \"downloading.\" The files are separated into directories that can be viewed prior to selecting files to download."}], "metadata": {"source": "Computer Security Bulletin Board System_ User's Guide", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guidelines on PDA Forensics provide?"}, {"role": "assistant", "content": "\n\nSpecial Publication 800-72 Sponsored by the Department of Homeland Security\n\n## Guidelines on PDA Forensics\n\n## Recommendations of the National Institute of Standards and Technology\n\nWayne Jansen Rick Ayers\n\nNIST Special Publication 800-72\n\n## Guidelines on PDA Forensics\n\nRecommendations of the National Institute of Standards and Technology\n\nWayne Jansen Rick Ayers\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nNovember 2004\n\n\n\n## U.S. Department of Commerce\n\nDonald L. Evans, Secretary\n\n## Technology Administration\n\nPhillip J. Bond, Under Secretary for Technology\n\nNational Institute of Standards and Technology\n\nArden L. Bement, Jr., Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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. National Institute of Standards and Technology Special Publication 800-72 Natl. Inst. Stand. Technol. Spec. Publ."}], "metadata": {"source": "Guidelines on PDA Forensics", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n| Device Cybersecurity Capability | Common Elements | Rationale | IoT Reference Examples | |--------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Data Protection : The IoT device can protect the data it stores and transmits from unauthorized access and modification."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\n| Executive Summary . . . . . . . . . . | Executive Summary . . . . . . . . . . | . . . . . . . . . . . | 1 |\n|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1. Introduction . . . . . . . . . | 1. Introduction . . . . . . . . . | . . . . . . . . . . . . . . | 3 |\n| 1.1. Document Purpose and Scope | 1.1. Document Purpose and Scope | . . . . . . . . . | 7 |\n| 1.2. Intended Audience . . | 1.2. Intended Audience . . | . . . . . . . . . . . . . . | 7 |\n| 1.3. Organization . . . . | 1.3. Organization . . . . | . . . . . . . . . . . . . . . | 8 |\n| Introducing De-Identifcation . | Introducing De-Identifcation . | . . . . . . . . . . . . | 9 |\n| 2.1. Historical Context . . | 2.1. Historical Context . . | . . . . . . . . . . . . . . | 9 |\n| 2.2. Terminology . . . . | 2.2. Terminology . . . . | . . . . . . . . . . . . . . . . | 12 |\n| Governance and Management of Data De-Identifcation . . | Governance and Management of Data De-Identifcation . . | Governance and Management of Data De-Identifcation . . | 18 |\n| 3.1. Identifying the Goals and Intended Uses of De-Identifcation . . . . . | 3.1. Identifying the Goals and Intended Uses of De-Identifcation . . . . . | 3.1. Identifying the Goals and Intended Uses of De-Identifcation . . . . . | 18 |\n| 3.2. | Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "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 Fiscal Year 2022 Cybersecurity and Privacy Annual Report provide?"}, {"role": "assistant", "content": "\n\n## 2022 Cybersecurity & Privacy Annual Report\n\n\n\n## NIST Special Publication\n\n## Fiscal Year 2022 Cybersecurity and Privacy Annual Report\n\n| Patrick O'Reilly, Editor Computer Security Division Information Technology Laboratory | Co-Editors: Larry Feldman Greg Witte |\n|----------------------------------------------------------------------------------------------|----------------------------------------|\n| Kristina Rigopoulos, Editor Applied Cybersecurity Division Information Technology Laboratory | Huntington Ingalls Industries |\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-225\n\nMay 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\n\n\n\n\n## Foreword 5\n\n## Priority Areas\n\n| Cryptography | 7 |\n|---------------------------------------------|-----|\n| Education, Training & Workforce Development | 9 |\n| Identity & Access Management | 11 |\n| Privacy | 13 |\n| Risk Management & Measurement | 15 |\n| Trustworthy Networks & Platforms | 17 |\n| Usable Cybersecurity | 19 |\n| NCCoE Summary | 21 |\n| Opportunities to Engage | |\n\n22\n\nForeword\n\n\n\n## FOREWORD\n\nNelson Mandela famously said, 'Remember to celebrate milestones as you prepare for the road ahead.' This year, we celebrated a major milestone that we're proud of: 50 years of cybersecurity at NIST. Over the last five decades, we have conducted research and developed guidance that has led to extraordinary advancements in cybersecurity."}], "metadata": {"source": "Fiscal Year 2022 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\n3.3.3 | Validated Cryptography... 3.3.3. 3.3.3 Validated Cryptography\n\nThe cryptographic module used by the server shall be a FIPS 140-validated cryptographic module [50, 51]."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "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 Maintenance?"}, {"role": "assistant", "content": "According to Getting Ready for Post-Quantum Cryptography_ Exploring Challenges Associated with Adopting and Using Post-Quantum Cryptographic Algorithms:\n\nWhile some components of some systems tend to be replaced by improved components on a relatively frequent basis (e.g., cell phones), other components are expected to remain in place for a decade or more (e.g., components in electricity generation and distribution systems). Communications interoperability and records archiving requirements introduce additional constraints on system components. As a general rule, cryptographic algorithms cannot be replaced until all components of a system are prepared to process the replacement. Updates to protocols, schemes, and infrastructures often must be implemented when introducing new cryptographic algorithms. Consequently, algorithm replacement can be extremely disruptive and often takes decades to complete.\n\nSimilarly, cybersecurity standards and guidelines and the operational directives and mandates derived from them generally specify or presume the use of public-key cryptography. There is currently no inventory of these that can guide updates to the standards, guidelines, and regulations necessary to accommodate the migration to post-quantum cryptography."}], "metadata": {"source": "Getting Ready for Post-Quantum Cryptography_ Exploring Challenges Associated with Adopting and Using Post-Quantum Cryptographic Algorithms", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\nEncryption.....................................................................................................3-4 | | | | | 3.2.3 Data Integrity ................................................................................................3-5 | | | | | 3.2.4 Replay Protection .........................................................................................3-6 | | | | | 3.2.5 Availability.....................................................................................................3-6 | | | | 3.3 | Brief Overview of IEEE 802.11i Security..................................................................3-6 | | | | 3.4 | Summary..................................................................................................................3-9 | | | | Security Framework for Robust Security Networks | .....................................................4-1 | | | | 4.1 | Features of RSNs ....................................................................................................4-1 | | | | 4.2 | Key Hierarchies and Key Distribution and Management .........................................4-3 | | | | | 4.2.1 Pairwise Key Hierarchy ................................................................................4-4 | | | | | 4.2.2 Group Key Hierarchy....................................................................................4-7 | | | | 4.3 | Overview of RSN Data Confidentiality and Integrity Protocols ................................4-7 4.3.1 Temporal Key Integrity Protocol (TKIP)........................................................4-8 | | | | | 4.3.2 Counter Mode with Cipher Block Chaining MAC Protocol (CCMP)............4-10 | | | | 4.4 | Summary................................................................................................................4-14 | | | | Robust | Security Networks Principles of Operation......................................................5-1 | | | | 5.1 | General Principles of IEEE 802.11 Operation..........................................................5-1 | | | | | 5.1.1 IEEE 802.11 Frame Types | ...........................................................................5-1 | | | | 5.1.2 IEEE 802.11 Data Frame Structure..............................................................5-3 | | | | 5.2 | Phases of IEEE 802.11 RSN Operation"}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "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 Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n- Prioritize the patch. A patch may be a higher priority to deploy than others because its deployment would reduce cybersecurity risk more than other patches would. Another patch may be a lower priority because it addresses a low-risk vulnerability on a small number of low-importance assets. - Schedule patch deployment. Many organizations schedule patch deployments as part of their enterprise change management activities. - Acquire the patch. Patches may be downloaded from the internet, built internally by developers or system administrators, or provided through removable media. - Validate the patch. A patch's authenticity and integrity should be confirmed, preferably by automated means, before the patch is tested or installed. The patch could have been acquired from a rogue source or tampered with in transit or after acquisition. - Test the patch. A patch may be tested before deployment. This is intended to reduce operational risk by identifying problems with a patch before placing it into production. Testing may be performed manually or through automated methods. - Distribute the patch. Distributing the patch to the assets that need to have it installed can be organization-controlled (and occur automatically, manually, or as scheduled) or vendor-controlled, such as delivered from the cloud. - Validate the patch. As discussed in Section 2.3.1, a patch's authenticity and integrity should be confirmed before installation, preferably through automated means. - Install the patch. Installation can occur in numerous ways, including automatically; manually when directed to do so by a user, administrator, vendor, or tool; as a result of other software being installed or updated; and through the replacement of removable media used by an asset. Some installations require administrator privileges, such as installing firmware patches for a system basic input/output system (BIOS). 3 Some patch installations require user participation or cooperation."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to A Threat Analysis on UOCAVA Voting Systems:\n\nFinally, there are some difficulties common to absentee voting. One such difficulty is with signature verification. Signatures are the most common method for authenticating voters. However, verifying signatures is a difficult task. In order to verify a signature, a trusted sample signature must be on file with election officials. Comparing a received signature with a signature on file requires a great deal of training, although automated signature verification applications may make this task easier.\n\nThe section documents threats to the transmission options for the Ballot Distribution stage. This section discusses threats to systems which use postal mail, fax machines, electronic mail, and web sites to distribute blank ballots to registered UOCAVA voters. The systems analyzed in this section are discussed in Section 4.3. Note that telephone systems are not considered in this section. Telephone voting systems provide voters with ballot questions and allow voters to select their votes. Therefore, telephone voting systems are a type of ballot return system, and are discussed in Section 6.3.2.\n\nauthentication occurs in the registration phase, where some type of authenticator (typically a voter signature) is exchanged. This authenticator must be securely stored by election officials so that it is available to authenticate future correspondence from a voter. While some authenticators, such as PINs, are easy to verify, training is necessary to verify authenticators like voter signatures."}], "metadata": {"source": "A Threat Analysis on UOCAVA Voting Systems", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements\n\nNIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-02-23\n\n## How to Cite this NIST Technical Series Publication\n\nScarfone KA, Souppaya MP, Fagan MJ (2024) Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines: Developing Cybersecurity and Privacy Concept Mappings. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8477. https://doi.org/10.6028/NIST.IR.8477\n\n## Author ORCID iDs\n\nKaren Scarfone: 0000-0001-6334-9486\n\nMurugiah Souppaya: 0000-0002-8055-8527\n\nMichael Fagan: 0000-0002-1861-2609\n\n## Contact Information\n\nmapping@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8477/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA)."}], "metadata": {"source": "Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\n3.2.1 | Data Breach and Data Exposure... 3.2.1 Data Breach and Data Exposure\n\nA data breach is an incident that involves sensitive, protected information being copied, transmitted, viewed, deliberately exposed to the public, or used by individuals or entities unauthorized to do so."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "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 Service Mesh Proxy Models for Cloud-Native Applications provide? (Part 5)"}, {"role": "assistant", "content": "publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication.\n## Table of Contents\n\n| Executive Summary............................................................................................................................1 | Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 | 1. Introduction...................................................................................................................................2 |\n| 2. Typical Service Mesh Data Plane Capabilities and Associated Proxy Functions .................................5 | 2. Typical Service Mesh Data Plane Capabilities and Associated Proxy Functions .................................5 |\n| 3. Proxy Models (Data Plane Architectures) in Service Mesh Implementations ....................................7 | 3. Proxy Models (Data Plane Architectures) in Service Mesh Implementations ....................................7 |\n| 4. Data Plane Architecture Threat Scenarios and Analysis Methodology............................................12 | 4."}], "metadata": {"source": "Service Mesh Proxy Models for Cloud-Native Applications", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters:\n\nSimply deleting e-mails from servers and clients does not typically remove all traces of those e-mails on those systems. Due to the way that e-mails are typically stored on servers and clients, file-level sanitization software cannot be relied upon to securely erase this data. These computer systems should be treated as any other containing potentially sensitive data, and sanitizing storage media prior to decommissioning or repurposing. Section 4.2.4 of NISTIR 7682 provides best practices for decommissioning systems."}], "metadata": {"source": "Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security of Interactive and Automated Access Management Using Secure Shell (SSH):\n\nolate policies, such as leading from development and test systems into production systems, or crossing from a low-impact system to a high-impact system without requiring any additional authentication.\nMost importantly, SSH key-based trust relationships can enable an attacker who compromises one system to quickly move (or pivot) from one system to another and spread through an organization-individual trust relationships often collectively form webs of trust across an organization's systems."}], "metadata": {"source": "Security of Interactive and Automated Access Management Using Secure Shell (SSH)", "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 Security Analysis of First Responder Mobile and Wearable Devices:\n\n| Threats to Public Safety Wearable Devices..................................................\n| 42 |\n| 7.4 | Areas Warranting Further Scrutiny................................................................ | 49 |\n| 8 Security Objectives..............................................................................................53 | 8 Security Objectives..............................................................................................53 | |\n| 8.1 | Availability..................................................................................................... | 53 |\n| 8.2 | Ease of Management.................................................................................... | 54 |\n| 8.3 | Interoperability .............................................................................................."}], "metadata": {"source": "Security Analysis of First Responder Mobile and Wearable Devices", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2013 Annual Report:\n\nEvaluation\n\n| Welcome Letter | ..................................................................1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|\n| Computer Security Division (CSD) Management Team.......2 | |\n| Computer Security Division Organization | ..........................3 |\n| The Computer Security Division Implements the Federal Information Security Management Act | .................7 |\n| Program & Project Achievements for Fiscal Year 2013 | .....9 |\n| NIST Responsibilities Under Executive Order 13636, 'Improving Critical Infrastructure Cybersecurity' | ....................10 |\n| Contributions to National and International Standards Development...........................................................................11 | |\n| Identity Management Standards within INCITS B10 and ISO JTC1/SC 17 ................................................................"}], "metadata": {"source": "Computer Security Division 2013 Annual Report", "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 Best Practices for Privileged User PIV Authentication:\n\n| NIST SP 800-53 Control Number and Name | Applicability to Privileged User Authentication |\n|--------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|\n| IA-2, Identification and Authentication (Organizational Users) | Uniquely identify and authenticate each privileged user. Also, see IA-2 control enhancements (1), (3), (6), (8), (11), and (12). |\n| IA-4, Identifier Management | Manage information system identifiers for all privileged users. |\n| IA-5, Authenticator Management | Manage information system authenticators for all privileged users. IA-5 control enhancements of particular interest include (1), (2), and (11). |\n| IA-8, Identification and Authentication (Non-Organizational Users) | Uniquely identify and authenticate each privileged user. Also, see IA-8 control enhancements (1) and (5). |\n| SC-8, Transmission Confidentiality and Integrity | Protect the confidentiality and integrity of all communications related to privileged user authentication and privileged sessions. |\n| SC-10, Network Disconnect | Terminate network connections from privileged accounts after a defined period of inactivity. |\n| SI-2, Flaw Remediation | Apply patches and other updates to correct vulnerabilities in protocols, services, etc. used for privileged user authentication. |\n| SI-4, Information System Monitoring | Perform ongoing monitoring of all privileged account usage. SI-4 control enhancements of particular interest include (20). |"}], "metadata": {"source": "Best Practices for Privileged User PIV Authentication", "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 Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc. provide?"}, {"role": "assistant", "content": "\n\n## CASE STUDIES IN CYBER SUPPLY CHAIN RISK MANAGEMENT\n\nObservations from Industry\n\n## Palo Alto Networks, Inc. ## INTERVIEWEES:\n\nJason Ledgerwood - VP Supply Chain Operations and Procurement\n\nBrian Riggs - Sr. Director, Supply Base Management\n\nJim Sugg - Sr. Product Manager\n\nShae Trautwein - Supply Chain Risk and Compliance Manager\n\nFebruary 4, 2020\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.CSWP.02042020-6\n\nJon Boyens\n\nCelia Paulsen Computer Security Division\n\nInformation Technology Laboratory\n\nNadya Bartol Kris Winkler James Gimbi\n\nBoston Consulting Group\n\n## SERIES DESCRIPTION\n\nThe Case Studies in Cyber Supply Chain Risk Management series engaged with several companies that are mature in managing cyber supply chain risk. These case studies build on the Best Practices in Cyber Supply Chain Risk Management case studies originally published in 2015 with the goals of covering new organizations in new industries and bringing to light any changes in cyber supply chain risk management practices. For information on NIST's Cyber Supply Chain Risk Management project, see https://csrc.nist.gov/projects/cyber-supply-chain-risk-management. ## DISCLAIMER\n\nAny mention of commercial products or organizations is for informational purposes only; it is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the products identified are necessarily the best available for the purpose."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\n3.5.4 IT Infrastructure Maintenance Information Type | ... 3.5.4 IT Infrastructure Maintenance Information Type\n\nIT infrastructure maintenance involves the planning, design, implementation, and maintenance of an IT Infrastructure to effectively support automated needs (i."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "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 is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to A Formal Description of the SDNS Security Protocol at Layer 4 (SP4):\n\n3.2.2 Connectionless Network Interface\n\nThe use of the connectionless Network service interface for the SP4E Entity poses an additional challenge for the specification."}], "metadata": {"source": "A Formal Description of the SDNS Security Protocol at Layer 4 (SP4)", "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 De-Identifying Government Datasets_ Techniques and Governance provide? (Part 4)"}, {"role": "assistant", "content": "h to use de-identification. Before using de-identification, agencies should evaluate their goals for using de-identification and the potential risks that releasing de-identified data might create.\nAgencies should decide upon a data-sharing model, such as publishing de-identified data, publishing synthetic data based on identified data, providing a query interface that incorporates de-identification, or sharing data in non-public protected enclaves. Agencies can create a Disclosure Review Board to oversee the process of de-identification. They can also adopt a de-identification standard with measurable performance levels and perform re-identification studies to gauge the risk associated with de-identification. Several specific techniques for de-identification are available, including de-identification by removing identifiers, transforming quasi-identifiers, and generating synthetic data using models. People who perform de-identification generally use special-purpose software tools to perform the data manipulation and calculate the likely risk of re-identification. However, not all tools that merely mask personal information provide sufficient functionality for performing de-identification. This document also includes an extensive list of references, a glossary, and a list of specific de-identification tools, which is only included to convey the range of tools currently available and is not intended to imply a recommendation or endorsement by NIST. ## Keywords\n\ndata life cycle; de-identification; differential privacy; direct identifiers; Disclosure Review Board; k-anonymity; privacy; pseudonymization; quasi-identifiers; re-identification; synthetic data; The Five Safes. ## 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": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\nThe Identify Function is foundational to cybersecurity and the risk management process. Cybersecurity assessments and risk management should start with the Identify Function. Consideration of the organization's mission objectives, business objectives, threat environment, assets, and vulnerabilities will have a significant influence on the overall risk management decision and will impact the other four Functions (i.e., Protect, Detect, Respond, Recover). | Subcategory | Applicability to HSNs | Informative References |\n|-----------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|\n| ID.BE-1: The organization's role in the supply chain is identified and communicated. | Identify the role in the supply chain and consider any partners' role in the supply chain. Clearly communicate any corresponding expectations and requirements."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "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 AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\n3.3.2 | High Availability and Scalability | ... 3.3.2 High Availability and Scalability\n\nTwo other important features for SSL VPNs are high availability and scalability."}], "metadata": {"source": "Guide to SSL VPNs", "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 Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-06-29 Supersedes NIST SP 800-219 (June 2022) https://doi.org/10.6028/NIST.SP.800-219\n\n## How to Cite this NIST Technical Series Publication:\n\nTrapnell M, Trapnell E, Souppaya MP, Gendler B, Brodjieski D, Golbig A, Scarfone K, Heiserman B (2023) Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-219r1. https://doi.org/10.6028/NIST.SP.800-219r1\n\n## Author ORCID iDs\n\nMark Trapnell: 0000-0002-5266-3610\n\nEric Trapnell: 0000-0001-9315-3732\n\nMurugiah Souppaya: 0000-0002-8055-8527\n\nBob Gendler: 0000-0002-8928-6492\n\nKaren Scarfone: 0000-0001-6334-9486\n\n## Contact Information\n\napplesec@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThe macOS Security Compliance Project (mSCP) provides resources that system administrators, security professionals, security policy authors, information security officers, and auditors can leverage to secure and assess macOS desktop and laptop system security in an automated way. This publication introduces the mSCP and gives an overview of the resources available from the project's GitHub site, which is continuously curated and updated to support each new release of macOS."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series:\n\nAES; block cipher; cryptography; mode of operation; SP 800-38; standardization; Triple-DES.\n\nNIST Interagency or Internal Report (NIST IR) 8319 [55] focuses on the Advanced Encryption Standard (AES) [22] that was standardized in FIPS 197 [58]. AES is one of only two block ciphers that are currently standardized by NIST. The other is the Triple Data Encryption Algorithm (TDEA) [10], also known as Triple-DES (Data Encryption Standard). Triple-DES is deprecated and will be disallowed after 2023 [11]. A block cipher can only process inputs of a specific length, known as the block size. AES has a block size of 128 bits, and Triple-DES has a block size of 64 bits. To process inputs of other lengths, it is necessary to use a mode of operation. A mode of operation can process shorter or larger inputs by performing one or more calls to an underlying block cipher. In fact, it is possible to claim that a block cipher is always used in combination with a mode of operation: using a block cipher 'directly' is equivalent to using it in the Electronic Codebook (ECB) mode with the restriction that the input must be exactly one block in length (e.g., 128 bits in the case of AES). Therefore, the real-world applications of the NIST-recommended modes of operation overlap with the applications of the underlying block cipher and include virtually all web browsers, Wi-Fi and cellular devices, and contact and contactless chip cards, as described in NIST IR 8319 [55]. operation. This report analyzes the block cipher modes of operation that are standardized in\n\nNote that NIST SP 800-38G [32], which defines the Format-Preserving Encryption (FPE) modes FF1 and FF3, is currently undergoing a revision that is proposed in Draft NIST SP 80038G, Rev. 1 [33]."}], "metadata": {"source": "Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Module-Lattice-Based Digital Signature Standard:\n\n3.4.2. 3.4.2. 3.4.2."}], "metadata": {"source": "Module-Lattice-Based Digital Signature Standard", "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 Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication NIST SP 800-221A\n\n## Information and Communications Technology (ICT) Risk Outcomes\n\nIntegrating ICT Risk Management Programs with the Enterprise Risk Portfolio\n\nStephen Quinn Nahla Ivy Julie Chua Karen Scarfone Matthew Barrett Larry Feldman Daniel Topper Greg Witte\n\nR. K. Gardner\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-221A\n\n\n\n## NIST Special Publication NIST SP 800-221A\n\n## Information and Communications Technology (ICT) Risk Outcomes\n\nIntegrating ICT Risk Management Programs with the Enterprise Risk Portfolio\n\n## Stephen Quinn\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nNahla Ivy\n\nEnterprise Risk Management Office Office of Financial Resource Management\n\nJulie Chua\n\nOffice of Information Security\n\nOffice of the Chief Information Officer (OCIO) U.S. Department of Health and Human Services\n\nKaren Scarfone Scarfone Cybersecurity\n\nMatthew Barrett CyberESI Consulting Group, Inc. Larry Feldman Daniel Topper Greg Witte Huntington Ingalls Industries\n\nR. K. Gardner New World Technology Partners\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-221A\n\nNovember 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities."}], "metadata": {"source": "Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.7 (NIST 3.1.7)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.1.7. 3.1.7."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "nist_control": "3.1.7", "cmmc_practice_id": "AC.L2-3.1.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog:\n\n| 29 | | (AEI) Access to Event Information | ................................................................29 | | (EIM) Event Identification & Monitoring | .........................................................29 | | (EVR) Event Response.................................................................................30 | | | (LCT) Logging Capture & Trigger Support | ....................................................31 | | (RDL) Support of Required Data Logging | .....................................................31 | | (LSR) Audit Log Storage & Retention ...........................................................32 | | | (SRT) Support for Reliable Time...................................................................32 | | | (AUP) Audit Support & Protection .................................................................33 | | | (AWR) State Awareness Support..................................................................34 | | | DS - DEVICE SECURITY ....................................................................................."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities provide? (Part 5)"}, {"role": "assistant", "content": "orkshop and received over 150 position papers, many of which suggested secure software development practices, tasks, examples of implementations, and references for consideration for this SSDF update.\nThe authors appreciate all of those suggestions, as well as the input from those who spoke at or attended the workshop and shared their thoughts during or after the workshop. Additionally, the authors appreciate the public comments submitted by dozens of organizations and individuals and wish to acknowledge the particularly helpful feedback from Amazon Web Services, Apiiro, Blackberry, BSA | The Software Alliance, the Enterprise Cloud Coalition, the General Services Administration (GSA), Google, IBM, Medical Imaging & Technology Alliance (MITA), Microsoft, Oracle, the Software Assurance Forum for Excellence in Code (SAFECode), Synopsis, the U.S. Navy, Xoomworks, and Robert Grupe. Representatives of Siemens Energy and Synopsis contributed mappings to new references. The authors thank all of their NIST colleagues for their support throughout the SSDF update, especially Curt Barker, Paul Black, Jon Boyens, Jim Foti, Barbara Guttman, Mat Heyman, Nicole Keller, Matt Scholl, Adam Sedgewick, Kevin Stine, and Isabel Van Wyk. The authors also wish to thank all of the individuals and organizations who provided comments on drafts of the original version of the SSDF, including the Administrative Offices of the U.S. Courts, The Aerospace Corporation, BSA | The Software Alliance, Capitis Solutions, the Consortium for Information & Software Quality (CISQ), HackerOne, Honeycomb Secure Systems, iNovex, Ishpi Information Technologies, the Information Security and Privacy Advisory Board (ISPAB), Juniper Networks, Microsoft, MITA, Naval Sea Systems Command (NAVSEA), NIST, Northrop Grumman, the Office of the Undersecretary of Defense for Research and Engineering, Red Hat, SAFECode, and the Software Engineering Institute (SEI)."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities:\n\nIf vulnerability characteristics related to these two concepts were measured and documented in a consistent, methodical way, the measurement data could be used by quantitative risk assessment methodologies for determining which vulnerabilities are most important for an organization to address using its limited resources. For example, when planning the security configuration settings for a new system, an organization could use vulnerability measurements as part of determining the relative importance of particular settings and identifying the settings causing the greatest increase in risk. Vulnerability measurement is also useful when evaluating the security of software features, such as identifying the vulnerabilities in those features that should have compensating controls applied to reduce their risk (for example, antivirus software to scan email attachments and awareness training to alter user behavior) and determining which features should be disabled because their risk outweighs the benefit that they provide.\n\nThe Exploitation Method metric is not used directly in generating CCSS scores, but the definitions for some of the Exploitability base metrics are dependent on the value of the Exploitation Method metric. The Exploitation Method metric is also useful for planning mitigation strategies, because most Passive configuration issues involve an error or policy violation that can be fixed quickly. Active configuration issues have a much wider range of mitigation possibilities and often require significantly more analysis and planning for mitigation than Passive configuration issues."}], "metadata": {"source": "The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.6 (NIST 3.3.6)?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\n3.3.6 | Access Control ... 3.3.6 Access Control\n\nSSL VPN products vary greatly in their access control features."}], "metadata": {"source": "Guide to SSL VPNs", "cmmc_level": "all", "nist_control": "3.3.6", "cmmc_practice_id": "AU.L2-3.3.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Computer Security_ Selected Articles:\n\nThis National Institute of Standards and Technology Internal Report (NISTIR) presents nine articles which represent a wide spectrum of computer security information. The articles were selected by the staff of the Computer Security Division, Computer Systems Laboratory, at the National Institute of Standards and Technology. The information provided is by no means comprehensive; rather the articles offer a quick reference or an introduction to a specific security technology. The article \"Is your System Safe?\" is a high-level overview of the Internet worm and addresses ways to correct various system vulnerabilities. The article \"Computer Viruses and Personal Computers\" provides guidance on preventing and handling computer viruses. The remaining articles discuss software copying, local-area-network security, computer ethics, data security responsibilities, risk analysis, and encryption. This publication will benefit computer security managers as well as managers and users of information technology.\n\nThe second part of this document contains a reading list prepared by the Information Exchange Working Group of the Computer and Telecommunications Security Council, a govemment/industry technical group that was sponsored by NIST from 1987 to 1990. The list provides titles, sources, and abstracts of important computer security publications that were relevant to the council's interests.\n\nWhat's the solution when you have a legitimate need for dial out 7 Start by using a communications server. A communications server is a separate machine on the LAN that allows network users to connect to the outside wono througn one modem. To make this more attractive, you might consider a combination facsimile and modem board: you have the advantage of making both dial out and fax available to all network users."}], "metadata": {"source": "Computer Security_ Selected Articles", "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 Guidelines for Derived Personal Identity Verification (PIV) Credentials:\n\n-  X.509 Certificate for Digital SignatureThe read access control rule for the X.509 Certificate for Digital Signature and the PKI cryptographic function access rule for the corresponding private key are as described in Section 3.2.1 of [SP800-73Part1] .\n-  X.509 Certificate for Key ManagementThe read access control rule for the X.509 Certificate for Key Management and the PKI cryptographic function access rule for the corresponding private key are as described in Section 3.2.2 of [SP800-73Part1] .\n-  Discovery ObjectThe requirements for the Discovery Object are as described in Section 3.3.2 of [SP800-73Part1] except for the following:\n- o References to 'PIV Card Application AID' are replaced by 'Derived PIV Application AID.'\n- o References to 'PIV Card Application PIN' are replaced by 'Derived PIV Application"}], "metadata": {"source": "Guidelines for Derived Personal Identity Verification (PIV) Credentials", "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 Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\n\n| 1 | Introduction ............................................................................................................1 | Introduction ............................................................................................................1 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 2 | Hardware Platform Security Overview .................................................................3 | Hardware Platform Security Overview .................................................................3 | | 3 | Platform Integrity Verification...............................................................................5 | Platform Integrity Verification...............................................................................5 | | | 3.1 Hardware Security Module (HSM) | .................................................................."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4):\n\n3.3.2."}], "metadata": {"source": "Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4)", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh:\n\nAHLC-SR-2 : Host path volumes should not be used, because they create tight coupling between the container and the node on which it is hosted, constraining the migration and flexible resource scheduling process. | TAG | RECOMMENDATION TEXT | FRAMEWORK AREA |\n|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|\n| ISMC-SR-1 | If certificate-based authentication is used for authenticating service calls, the signing certificate used by the service mesh's CA module should be rooted in the organization's existing PKI to allow for auditability, rotation, and revocation. | Initial Service Mesh Configuration |\n| ISMC-SR-2 | Communication between the service mesh control plane and the application orchestration and resource management platform's configuration server must be authenticated and authorized. | Initial Service Mesh Configuration |\n| A HLC-SR-1 | Containers and applications should not be run as root (thus becoming privileged containers). In Kubernetes, the configuration setting for this is to set the value TRUE for 'MustRunAsNonRoot' flag."}], "metadata": {"source": "Attribute-based Access Control for Microservices-based Applications using a Service Mesh", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Application Container Security Guide:\n\n3.2.1 レジストリへのセキュアでない接続 ... 3.2.1 レジストリへのセキュアでない接続\n\nイメージには組織独自のソフトウェアや埋め込まれた秘密情報など、機微なコンポーネントが含まれていることがよ くある。レジストリへの接続が、セキュアでないチャネルで行われた場合、イメージの内容は、平文で送信される他 のデータと同様の機密性に対するリスクにさらされる。また、レジストリを対象としているネットワークトラフィッ クを傍受し、そのトラフィック内の開発者や管理者の認証情報を盗み出し、詐欺的なイメージや古いイメージをオー ケストレータに提供したりする中間者攻撃のリスクも高まる。\n\n## 3."}], "metadata": {"source": "Application Container Security Guide", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Computer Security Division 2015 Annual Report:\n\nIn FY 2016, NIST will continue to conduct stakeholder outreach and will work collaboratively to further understand stakeholder needs regarding tools and resources to enable more effective use of the Framework. NIST will also publish guidance on how NIST's Risk Management Framework (SP 800-37 revision 1) and the Cybersecurity Framework complement each other. Additionally, NIST will formally gather stakeholder input about Framework use, evolution, and future management through a request for information (RFI). Following the RFI, NIST will conduct a public workshop at NIST in Gaithersburg, Maryland on April 6 and 7, 2016. Periodic program updates will be provided through the Framework website. - Finalize SP 800-16, A Role-Based Model for Federal Information Technology / Cybersecurity Training;\n- Begin the development of SP 800-53, Revision 5, Security and Privacy Controls for Federal Information Systems and Organizations;\n- Continue to explore ways to use automation to support SP 800-53 updates;\n- Continue the development of SP 800-60, Revision 2, Guide for Mapping Types of Information and Information Systems to Security Categories;\n- Continue the development of SP 800-18, Revision 2, Guide for Developing Security Plans for Federal Information Systems and Organizations;\n- Expand cybersecurity outreach to include additional state, local, and tribal governments, as well as private sector organizations and academic institutions;\n- Continue to support federal agencies in the effective implementation of the RMF; and\n- Continue collaboration with JTF partners and other federal organizations. In FY 2015, Biometric Conformance Test Software (BioCTS) for ANSI/NIST-ITL (which targets biometric transactions based on NIST SP 500-290, and SP 500-290 Revision 1 - Data Format for the Interchange of Fingerprint, Facial & Other Biometric Information) received a substantial update."}], "metadata": {"source": "Computer Security Division 2015 Annual Report", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | |\n|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings:\n\n| 1 | Introduction ............................................................................................................1 | Introduction ............................................................................................................1 |\n|--------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| 2 | 1.2 | About the IoT Cybersecurity Colloquium......................................................... 1 |\n| | Summary and Key Takeaways..............................................................................3 | Summary and Key Takeaways..............................................................................3 |\n| | 2.1 | Defining the Internet of Things........................................................................ 3 |\n| | 2.2 | IoT Cybersecurity and Privacy Risks .............................................................. 3 |\n| | 2.3 | IoT-Specific Risks ..........................................................................................."}], "metadata": {"source": "Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\n| Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi |\n|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ............................................................................................................1 | 1. Introduction ............................................................................................................1 | |\n| | Purpose and Scope | ........................................................................................ 1 |\n| | Audience........................................................................................................."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1 provide?"}, {"role": "assistant", "content": "\n\n## The Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.1\n\n## Recommendations of the National Institute of Standards and Technology\n\nDavid Waltermire Stephen Quinn Karen Scarfone\n\nNIST Special Publication 800-126 Revision 1\n\nThe Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.1\n\nRecommendations of the National Institute of Standards and Technology\n\nDavid Waltermire Stephen Quinn Karen Scarfone\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nFebruary 2011\n\n\n\nU.S. Department of Commerce\n\nGary Locke, Secretary\n\nNational Institute of Standards and Technology\n\nDr. Patrick D. Gallagher, Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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. National Institute of Standards and Technology Special Publication 800-126, Revision 1 39 pages (Feb."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to U.S. Department of Energy Risk Assessment Methodology:\n\n- . Excessively detailed and lengthy --making it a paper exercise rather than a beneficial management and security awareness process\n- . Overly quantitative in approach, thus resulting in an end-product that is difficult to interpret (if not useless)\n- Not oriented towards the true \"bottom-line\": \"What is it going to cost to fix the problems identified?\"\n\n- . Personnel Management\n- . Manufacturing/Control\n- . Mathematics/Statistical\n- . Security\n- . Training\n\n| ucrAK 1 Mcn 1 ur ADP SYSTEM RISK ASSESSMENT | ucrAK 1 Mcn 1 ur ADP SYSTEM RISK ASSESSMENT | CROSS REFERENCE NUMERIC LISTING OF DOE ORDERS USED TO DEVELOP SECURITY REQUIREMENTS | STEP 3 RESOURCE TABLE R3 (Page 3) |\n|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------------------|\n| OOe:;;::fi::::::.:::: OOCVMeNT NUMBER | DOE DOCMMBIT TITI^ (A» ^ | DOE DOCMMBIT TITI^ (A» ^ | BASELINE REQUIREMENT CODE |\n| 1000.38 | INTERNAL CONTROL SYSTEMS | INTERNAL CONTROL SYSTEMS | K, |\n| 1330.18 | MANAGEMENT OF AUTOMATED INFORMATION SYSTEMS AND DATA RESOURCES | MANAGEMENT OF AUTOMATED INFORMATION SYSTEMS AND DATA RESOURCES | C."}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "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 Biometric Specifications for Personal Identity Verification:\n\nn performance. A template generator is logically a converter of images to templates. A template matcher logically compares one or two templates with one or two templates to produce a similarity score.\nTemplate generators and template matchers shall be certified separately. This aspect is instituted because:"}], "metadata": {"source": "Biometric Specifications for Personal Identity Verification", "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 Media Protection?"}, {"role": "assistant", "content": "According to Codes for Identification of Federal and Federally-Assisted Organizations:\n\nns Command |\n| 573G | Air Force Elements, Europe |\n| 573I | Reservist, Centrally Managed |\n| 573K | HQ U.S.\nEuropean Command |\n| 573L | Center for Air Force History |\n| 573M | Air Force Elements, U.S. Southern Command |\n| 573N | Air Force Elements, U.S. Atlantic Command |\n| 573O | Air Force Elements, U.S. Pacific Command |\n| 573Q | Air Force Elements, U.S. Strategic Command |\n| 573R | Air Force Elements, U.S. Readiness Command |\n| 573S | Headquarters, U.S. Space Command and NORAD |\n| 573T | Air Force Elements U.S. Transportation Command |\n| 573V | Air Force Elements, Other than Europe |\n| 573W | Air Force Center for Environmental Excellence |\n| 573Y | Air Force Frequency Management Center |\n| 573Z | Joint Services Survival, Evasion, Resistance and Escape Agency |"}], "metadata": {"source": "Codes for Identification of Federal and Federally-Assisted Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\nes to mitigate malicious code threats are outside the scope of this document (see [SP 800-53] for a catalog of security and privacy controls for federal information systems).\nMalicious code could be introduced into PIN capture and biometric capture devices for the purpose of compromising or otherwise exploiting the PIV Card. General good practice to mitigate malicious code threats is outside of the scope of this document (see [SP 800-53] for a catalog of security and privacy controls for federal information systems)."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Security for Full Virtualization Technologies:\n\nThe hypervisor is responsible for managing guest OS access to hardware (e.g., CPU, memory, storage). The hypervisor partitions these resources so that each guest OS can access its own resources but cannot encroach on the other guest OSs' resources or any resources not allocated for virtualization use. This prevents unauthorized access to resources and also helps prevent one guest OS from injecting malware into another, such as infecting a guest OS's files or placing malware code into another guest OS's memory. Separately, partitioning can also reduce the threat of denial of service conditions caused by excess resource consumption in other guest OSs on the same hypervisor. Guest OSs are often not completely isolated from each other and from the host OS because that would prevent necessary functionality. For example, many hosted virtualization solutions provide mechanisms called guest tools through which a guest OS can access files, directories, the copy/paste buffer, and other resources on the host OS or another guest OS. These communication mechanisms can inadvertently serve as an attack vector, such as transmitting malware or permitting an attacker to gain access to particular resources. Bare metal virtualization software does not offer such sharing capabilities. Another potential problem with increasing the use of virtualization in particular is the proliferation of images, also known as sprawl . It is easy to create a new image-it can often be done in just a few minutes, albeit without any consideration of security-so unnecessary images may be created and run. Each additional image running is another potential point of compromise for an attacker. Also, each additional image is another image that has to have its security maintained. Therefore, organizations should minimize the creation, storage, and use of unnecessary images."}], "metadata": {"source": "Guide to Security for Full Virtualization Technologies", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to User's Guide to Telework and Bring Your Own Device (BYOD) Security:\n\n4 OMB Memorandum 06-19, Reporting Incidents Involving Personally Identifiable Information and Incorporating the Cost for Security in Agency Information Technology Investments, defines PII as 'any information about an individual maintained by an agency, including, but not limited to, education, financial transactions, medical history, and criminal or employment history and information which can be used to distinguish or trace an individual's identity, such as their name, social security number, date and place of birth, mother's maiden name, biometric records, etc., including any other personal information which is linked or linkable to an individual.' The full text of the memorandum is available at http://www.whitehouse.gov/omb/memoranda/fy2006/m-06-19.pdf.\n\nTeleworkers should also be aware of how to handle threats involving social engineering , which is a general term for attackers trying to trick people into revealing sensitive information or performing certain actions, such as downloading and executing files that appear to be benign but are actually malicious. For example, an attacker might approach a teleworker in a coffee shop and ask to use the computer for a minute or offer to help the teleworker with using the computer. Teleworkers should be wary of any requests they receive that could lead to a security breach or the theft of a telework device. Teleworkers should ask their organizations for training regarding how to recognize and handle social engineering attempts, if such training is not already being provided."}], "metadata": {"source": "User's Guide to Telework and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case provide? (Part 5)"}, {"role": "assistant", "content": "3, Revision 1 has been released, this implementation guide will be revised to include the updates in the Cybersecurity Framework Version 1.1 as well, and will be published as NISTIR 8183A, Revision 1.\n## Table of Contents\n\n| Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi |\n|-------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ............................................................................................................1 | 1. Introduction ............................................................................................................1 | 1. Introduction ............................................................................................................1 |\n| and Scope | Purpose | ........................................................................................"}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\ni | |----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.0 | Privacy Framework Introduction..........................................................................................1 | | | | Overview of the Privacy Framework......................................................................................................2 | | | | Privacy Risk Management......................................................................................................................2 | | | 1.2.1 Cybersecurity and Privacy Risk Management...................................................................................3 | 1.2.1 Cybersecurity and Privacy Risk Management...................................................................................3 | | | 1.2.2 Privacy Risk Assessment....................................................................................................................4 | 1.2.2 Privacy Risk Assessment....................................................................................................................4 | | | | Document Overview..............................................................................................................................5 | | | 2.0 | Privacy Framework Basics....................................................................................................6 | | | | Core........................................................................................................................................................6 | | | | Profiles ...................................................................................................................................................8 | | | | Implementation Tiers ............................................................................................................................8 | | | 3.0 | How to Use the Privacy Framework.....................................................................................9 | | | | Mapping to Informative References......................................................................................................9 | | | | Strengthening Accountability ..............................................................................................................10 | | | | Establishing or Improving a Privacy Program ......................................................................................11 | | | | Applying to the System Development Life Cycle .................................................................................12 | | | | Using within the Data Processing Ecosystem ......................................................................................13 | | | | Informing Buying Decisions .................................................................................................................14 | | | References .........................................................................................................................................15 | References .........................................................................................................................................15 | References .........................................................................................................................................15 | | Appendix A: Privacy Framework Core................................................................................................."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "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 The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n| 1 INTRODUCTION.................................................................................................................\n1 | 1 INTRODUCTION................................................................................................................. 1 |\n| 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 | 2 REPORTING CONVENTIONS.......................................................................................... 2 |\n| 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 | 3 PROFESSIONAL DEMOGRAPHICS............................................................................... 3 | 3 PROFESSIONAL DEMOGRAPHICS..............................................................................."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n## FIPS PUB 201-3\n\n## Federal Information Processing Standards Publication\n\n## (Supersedes FIPS 201-2)\n\n## Personal Identity Verification (PIV) of Federal Employees and Contractors\n\n## Category: Information Security Subcategory: Identity\n\nInformation Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8900\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.FIPS.201-3\n\nIssued January 2022\n\n\n\n## U.S. Department of Commerce\n\nGina M. Raimondo, Secretary\n\n## National Institute of Standards and Technology\n\nJames K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## FOREWORD\n\nThe Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology is the official series of publications relating to standards and guidelines adopted and promulgated under the provisions of the Federal Information Security Modernization Act (FISMA) of 2014. Comments concerning Federal Information Processing Standard publications are welcomed and should be addressed to the Director, Information Technology Laboratory, National Institute of Standards and Technology, 100 Bureau Drive, Stop 8900, Gaithersburg, MD 20899-8900. Charles H. Romine, Director Information Technology Laboratory\n\ni\n\n## ABSTRACT\n\nAuthentication of an individual's identity is a fundamental component of physical and logical access control. An access control decision must be made when an individual attempts to access security-sensitive buildings, information systems, and applications. An accurate determination of an individual's identity supports making sound access control decisions."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n3.3.1 | Program Size... 3.3.1 Program Size\n\nParticipants in both the focus groups and survey were asked how many people (including federal employees and contractors) were covered by the organization's security awareness program (i."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide to Attribute Based Access Control (ABAC) Definition and Considerations:\n\n2 Cryptographic binding is a methodology for providing integrity and authenticity to data and data relationships using wellknown cryptographic techniques. Cryptographic binding works by determining the hash value of each object attribute associated with a specific object and digitally signing the collection of hashed values. When the object is accessed, if the object signature fails, the attribute hash values are then compared to determine which element was modified since the last binding operation. Scalability, feasibility, and performance are important issues when considering the deployment of an ABAC product or technology. Enterprise ABAC-allowing an organization to have access to authorized objects managed by another organization in the same enterprise-requires complex interaction between ABAC components. Often these components are distributed throughout the enterprise across organization boundaries and sometimes on different networks. The larger and more diverse the enterprise, the more complex these interactions become. What may have been a simple request to access a document in a repository may now require a policy request from an enterprise service, multiple attributes from numerous logically and physically dispersed attribute sources, a third-party validation of the integrity of the object attributes bound to the document, and a decision made at one point in the enterprise while the enforcement of that decision occurs at a different point in the enterprise. Feasibility evaluation should check whether applications can support ABAC, either natively or through third-party applications. All of these potential interactions have a performance cost that must be evaluated when determining the scope of objects that may be shared through an enterprise ABAC implementation. To mitigate potential performance and scalability concerns, a variety of architectures should be considered."}], "metadata": {"source": "Guide to Attribute Based Access Control (ABAC) Definition and Considerations", "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 Module-Lattice-Based Key-Encapsulation Mechanism Standard provide? (Part 4)"}, {"role": "assistant", "content": "systems used or operated by federal agencies or by a contractor of an agency or other organization on behalf of an agency. They do not apply to national security systems as defined in 44 U.S.C. 3552.\nThis standard, or other FIPS or NIST Special Publications that specify alternative mechanisms, shall be used wherever the establishment of a shared secret key (or shared secret from which keying material can be generated) is required for federal applications, including the use of such a key with symmetric-key cryptographic algorithms, in accordance with applicable Office of Management and Budget and agency policies. The adoption and use of this standard are available to private and commercial organizations. 7. Implementations. A key-encapsulation mechanism may be implemented in software, firmware, hardware, or any combination thereof. For every computational procedure that is specified in this standard, a conforming implementation may replace the given set of steps with any mathematically equivalent set of steps. In other words, different procedures that produce the correct output for every input are permitted. NIST will develop a validation program to test implementations for conformance to the algorithms in this standard. Information about validation programs is available at https: //csrc.nist.gov/projects/cmvp. Example values will be available at https://csrc.nist.gov/proj ects/cryptographic-standards-and-guidelines/example-values. 8. Other Approved Security Functions. Implementations that comply with this standard shall employ cryptographic algorithms that have been approved for protecting Federal Government-sensitive information. Approved cryptographic algorithms and techniques include those that are either:\n2. (a) Specified in a Federal Information Processing Standards (FIPS) publication,\n3. (b) Adopted in a FIPS or NIST recommendation, or\n4. (c) Specified in the list of approved security functions in SP 800-140C. 9. Export Control."}], "metadata": {"source": "Module-Lattice-Based Key-Encapsulation Mechanism Standard", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Information System Security Best Practices for UOCAVA-Supporting Systems:\n\n| 1 INTRODUCTION .............................................................................................................................................................3 | 1 INTRODUCTION .............................................................................................................................................................3 | 1 INTRODUCTION .............................................................................................................................................................3 | 1 INTRODUCTION .............................................................................................................................................................3 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1.1 1.2 | PURPOSE AND SCOPE .....................................................................................................................................................3 INTENDED AUDIENCE ....................................................................................................................................................3 | PURPOSE AND SCOPE .....................................................................................................................................................3 INTENDED AUDIENCE ....................................................................................................................................................3 | PURPOSE AND SCOPE .....................................................................................................................................................3 INTENDED AUDIENCE ....................................................................................................................................................3 | | 2 OVERVIEW OF UOCAVA-SUPPORTING SYSTEMS ..............................................................................................5 | 2 OVERVIEW OF UOCAVA-SUPPORTING SYSTEMS ..............................................................................................5 | 2 OVERVIEW OF UOCAVA-SUPPORTING SYSTEMS ..............................................................................................5 | 2 OVERVIEW OF UOCAVA-SUPPORTING SYSTEMS ..............................................................................................5 | | 2.1 SYSTEM OVERVIEW.......................................................................................................................................................5 | 2.1 SYSTEM OVERVIEW.......................................................................................................................................................5 | 2.1 SYSTEM OVERVIEW.......................................................................................................................................................5 | 2.1 SYSTEM OVERVIEW.......................................................................................................................................................5 | | 2.1.1 Voter Registration and Ballot Request ..................................................................................................................5 2.1.2 Electronic Ballot Delivery .....................................................................................................................................5 2.2 IT AND NETWORKING COMPONENT OVERVIEW ............................................................................................................6 3 IDENTIFICATION AND AUTHENTICATION...........................................................................................................7 | 2.1.1 Voter Registration and Ballot Request ..................................................................................................................5 2.1.2 Electronic Ballot Delivery .....................................................................................................................................5 2.2 IT AND NETWORKING COMPONENT OVERVIEW ............................................................................................................6 3 IDENTIFICATION AND AUTHENTICATION...........................................................................................................7 | 2.1.1 Voter Registration and Ballot Request ..................................................................................................................5 2.1.2 Electronic Ballot Delivery .....................................................................................................................................5 2.2 IT AND NETWORKING COMPONENT OVERVIEW ............................................................................................................6 3 IDENTIFICATION AND AUTHENTICATION...........................................................................................................7 | 2.1.1 Voter Registration and Ballot Request ..................................................................................................................5 2.1.2 Electronic Ballot Delivery .....................................................................................................................................5 2.2 IT AND NETWORKING COMPONENT OVERVIEW ............................................................................................................6 3 IDENTIFICATION AND AUTHENTICATION...........................................................................................................7 | | 3.1 AUTHENTICATING PEOPLE.............................................................................................................................................9 | 3.1 AUTHENTICATING PEOPLE.............................................................................................................................................9 | 3.1 AUTHENTICATING"}], "metadata": {"source": "Information System Security Best Practices for UOCAVA-Supporting Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\nThe national and economic security of the United States depends on the reliable functioning of critical infrastructure. Cybersecurity threats exploit the increased complexity and connectivity of critical infrastructure systems, placing the Nation's security, economy, and public safety and health at risk. Similar to financial and reputational risk, cybersecurity risk affects a company's bottom line. It can drive up costs and impact revenue. It can harm an organization's ability to innovate and to gain and maintain customers.\n\nThe Framework is not a one-size-fits-all approach to managing cybersecurity risk for critical infrastructure. Organizations will continue to have unique risks - different threats, different vulnerabilities, different risk tolerances - and how they implement the practices in the Framework will vary. Organizations can determine activities that are important to critical service delivery and can prioritize investments to maximize the impact of each dollar spent. Ultimately, the Framework is aimed at reducing and better managing cybersecurity risks.\n\nThe Framework is a living document and will continue to be updated and improved as industry provides feedback on implementation. As the Framework is put into practice, lessons learned will be integrated into future versions. This will ensure it is meeting the needs of critical infrastructure owners and operators in a dynamic and challenging environment of new threats, risks, and solutions."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines:\n\nThis index is a list of certain requirements which must be considered by Federal technical and administrative personnel in order to comply with those provisions of the Privacy Act of 1974* relating to automated systems design and development. This index has been derived from the Office of Management and Budget (0MB) guidelines** for implementing those provisions. Each requirement listed contains a reference to an applicable part of the Privacy Act and to a page and column number of the 0MB guidelines as they appear in the Federal Register . Therefore, these documents must be used in conjunction with this index. Furthermore, a familiarity with these documents will increase the utility of this index.\n\nThis index is a list of certain requirements which must be considered by Federal technical and administrative personnel in order to comply with those provisions of the Privacy Act of 1974* relating to automated systems design and development . This index has been derived from the Office of Management and Budget (0MB) guidelines** for implementing those provisions Each requirement listed contains a reference to an applicable part of the Privacy Act and to a page and column number of the 0MB guidelines as they appear in the Federal Register . Therefore, these documents must be used in conjunction with this index. Furthermore , a familiarity with these documents will increase the utility of this index."}], "metadata": {"source": "Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium:\n\nIn the particular case under consideration, the AM equipment was delivered to the 'manufacturing' floor, unboxed and set up all without the awareness of the IT department. Once installed, the AM engineering team connected with the Enterprise Help Desk and requested '…can you help connect our new printer to the network?' Unwittingly, the request was executed. Needless to say, the original equipment manufacturer (OEM) was unable to connect to the AM equipment, since it was behind the corporate firewall. Subsequent requests were submitted to the Enterprise Help Desk requesting OEM access to the equipment through the Internet for finetuning. The printer was transferred to an open Internet connection normally provided to corporate guests. This channel is monitored yet it has minimal shielding. It was only after subsequent investigation by the information security team that it became clear that the 'printer' was in fact a metal DDM system, not a typical office document printer. Following this discovery, the security team has moved the printer to a secure and scrutinized subnet on the network. Now, additional security controls and enhanced logging occur routinely and yet where it is still possible for the engineering team to work directly through the network with the manufacturer."}], "metadata": {"source": "Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium", "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 Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\n## Access Control:\n\nAccess to IT and OT systems is based on the principle of least privilege depending on the user's role in the organization. Proper authorization and approval by the Director of Operations are required prior to granting access or operating any components of the manufacturing system. Controls are in place to restrict access through authentication methods and other technical means. Passwords are managed through a formal process and secure log-on procedures. Sensitive systems are explicitly identified and audited regularly.\n\n1. Employees must complete cybersecurity awareness training and agree to uphold the acceptable use policy.\n2. Employees must immediately notify the Director of Operations if an unescorted or unauthorized individual is found in the facility.\n3. Employees must always use a secure password on all systems as per the password policy. These credentials must be unique and must not be used on other external systems or services.\n4. Terminated employees must return all company records, in any format.\n5. Employees must verify with the Director of Operations that authorizations have been granted before allowing external personnel to connect to the IT or OT network.\n6. Employees must report any physical or cybersecurity incidents to the Director of Operations."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "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 Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities:\n\n## Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities\n\nGuide to Test, Training, and Exercise Programs for IT Plans and Capabilities\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities", "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 Security Considerations for Voice Over IP Systems:\n\nA careful assessment must be conducted to ensure that sufficient backup power is available for the office VOIP switch, as well as each desktop instrument. Costs may include electrical power to maintain UPS battery charge, periodic maintenance costs for backup power generation systems, and cost of UPS battery replacement. If emergency/backup power is required for more than a few hours, electrical generators will be required. Costs for these include fuel, fuel storage facilities, and cost of fuel disposal at end of storage life.\n\nelectrical generators will be required. Costs for these include fuel, fuel storage facilities, and cost of fuel disposal at end of storage life."}], "metadata": {"source": "Security Considerations for Voice Over IP 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 are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## 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-05-06\n\n## How to Cite this NIST Technical Series Publication\n\nMegas, K, Fagan M, Cuthill B, Hoehn B , Petrella E (2025) Workshop Summary Report for 'Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' . (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8572. https://doi.org/10.6028/NIST.IR.8572\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448\n\nMichael Fagan: 0000-0002-1861-2609\n\nBarbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8572/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis report summarizes discussions held at the March 5, 2025 \"Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' organized by the NIST Cybersecurity for the Internet of Things (IoT) program."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guidelines on Securing Public Web Servers:\n\n3.6.1 | Trusted Operating Systems... 3.6.1 Trusted Operating Systems\n\nTrusted operating systems (TOS) are security-modified or -enhanced OSs that include additional security mechanisms not found in most general-purpose OSs."}], "metadata": {"source": "Guidelines on Securing Public Web Servers", "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 Personnel Security?"}, {"role": "assistant", "content": "According to Computer Security Training & Awareness Course Compendium:\n\n- GBA 560 | 79 | | MANAGING COMPUTER SECURITY-MERGERS S, ACQISITIONS, AND DIVESTITURES | 67 |"}], "metadata": {"source": "Computer Security Training & Awareness Course Compendium", "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 Prioritizing Cybersecurity Risk for Enterprise Risk Management provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2025-02-24 Supersedes NIST IR 8286B (February 2022) https://doi.org/10.6028/NIST.IR.8286B\n\n## How to Cite this NIST Technical Series Publication\n\nQuinn SD, Ivy N, Barrett M, Witte GA, Gardner RK (2025) Prioritizing Cybersecurity Risk for Enterprise Risk Management. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency Report (IR) NIST IR 8286B-upd1. https://doi.org/10.6028/NIST.IR.8286B-upd1\n\n## Author ORCID iDs\n\nStephen D. Quinn: 0000-0003-1436-684X Nahla Ivy: 0000-0003-4741-422X Matthew Barrett: 0000-0002-7689-427X Gregory A. Witte: 0000-0002-5425-1097\n\n## Contact Information\n\nnistir8286@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8286/b/upd1/final, including related content, potential updates, and document history. ## All comments are subject to release under the Freedom of Information Act (FOIA)."}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 PE.L2-3.10.2 (NIST 3.10.2)?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 1 – General:\n\n3.10.2 Public Static Key Agreement Keys... 3.10.2 Public Static Key Agreement Keys\n\nIf an entity determines that the public static key-agreement key is lost or corrupted, the entity may recover in one of the following ways:\n\n1. 3.10.2 to remove the impression that archiving is only performed after the end of the cryptoperiod of a key (e."}], "metadata": {"source": "Recommendation for Key Management_ Part 1 – General", "cmmc_level": "all", "nist_control": "3.10.2", "cmmc_practice_id": "PE.L2-3.10.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 Codes for Identification of Federal and Federally-Assisted Organizations:\n\n| EXECUTIVE SUMMARY.................................................................................................................. | EXECUTIVE SUMMARY.................................................................................................................. |\n|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | INTRODUCTION ...................................................................................................................."}], "metadata": {"source": "Codes for Identification of Federal and Federally-Assisted Organizations", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program:\n\nAn information security measurement program can increase accountability by helping organizations identify if specific controls that are implemented correctly, are not implemented, or are ineffective. The continuous feedback provided by a structured measurement program supports regular internal communications that collect data about information security performance and risks for high-level members of the organization. Implementing an information security measurement program demonstrates an organizational commitment to proactive information security and continuous improvement. For example, organizations that use the Cybersecurity Capacity Maturity Model (CMM) may implement a measurement program as part of the goal of demonstrating the Level 4, 'Managed,' degree of performance. When using the appropriate measures, an information security measurement program enables organizations to quantify improvements in securing systems and demonstrate quantifiable progress in accomplishing strategic goals and objectives. More information on selecting measures can be found in SP 800-55v1."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "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 Minimum Security Requirements for Multi-User Operating Systems:\n\n--------|--------------|-------------------------------------------------------------|--------|\n| | Abstract | | ii |\n| 1.\n| Introduction | Introduction | 1-1 |\n| | 1.1 | Background | 1-1 |\n| | | 1.1.1 Trusted Computer System ^valuation Criteria (TCSEC) | 1-2 |\n| | 1.1.2 | Information Technology Security Evaluation Criteria (TTSEC) | 1-2 |\n| | | 1.1.3 Security Requirements in the Commercial Sector | 1-3 |\n| | | 1.1.4 System Security Study Committee | 1-4 |\n| | | 1.1.5 Federal Criteria Project | 1-5 |\n| | | 1.1.6 Minimum Security Requirements | 1-5 |\n| | 1.2 | Scope of the MSR | 1-6 |\n| | 1.3 | Audience | 1-6 |\n| | 1.4 | Terminology | 1-7 |\n| | 1.5 | Document Organization | 1-7 |\n| 2."}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Forensic Filtering of Cell Phone Protocols:\n\nPhone managers are sometimes turned to as a way to recover data when no suitable forensic tool is available. Phone managers are typically available from the manufacturer of the cell phone and kept up to date with support for newly released models. They allow various operations, including retrieval of core user data such as phonebook entries and photos. The forensic soundness of tools not designed specifically for forensic purposes are questionable, however [4]. In particular, phone managers have the ability to both read and write data to a phone, which is problematic from a forensic perspective, if used without applying proper testing and procedural controls. Many anecdotes exist of a practitioner accidentally or unknowingly writing data to a phone when using such a tool. Cell phone manufacturers such as Nokia, Motorola, and Samsung normally keep their phone manager software up to date for new and current phone models in the product line. Forensic specialists have long recognized the potential for phone managers as a tool for automated recovery of common types of core user data. Because phone managers are not forensically sound, additional steps must be followed to use them to recover data. They include validating the operation of the phone manager, testing and verifying the procedures to be followed for acquisition to safeguard against altering data on the phone, and producing a cryptographic hash of acquired data objects. Initial testing of the two prototype implementations indicate that the approach could provide a practical and effective solution for addressing the latency in forensic tool coverage of available phones. The basic technique described is extendable beyond the specific phone manager examples given."}], "metadata": {"source": "Forensic Filtering of Cell Phone Protocols", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to U.S. Department of Justice Simplified Risk Analysis Guidelines:\n\n- a. The minimum security requirements for PCs, mainframes, minicomputers, and other remotely accessed AISs, and application systems are listed in Sections 3.1, 3.2, and 3.3 of the Appendix. The requirements of each of these sections are divided into requirements for nonsensitive, sensitive, and classified processing for Sections 3.1 and 3.2, and nonsensitive and sensitive applications for Section 3.3. The minimum security requirements are hierarchical in structure, so that requirements for processing lower sensitivity levels also are applicable to all higher sensitivity levels. - b. This step requires a review of the minimum security requirements as listed in the Appendix for the AIS or application under evaluation. The review also requires an evaluation of the effectiveness of the in-place security measures in meeting the security requirement. The person conducting the risk analysis must identify all security measures implemented to comply with the minimum security requirements, assess their effectiveness in meeting the requirement, and document the results. Any of the minimum requirements that are not met will be addressed in Step 5 where the selection of additional countermeasures will be considered. 1. Description of Sensitivity and Criticality of Data Processed\n2. -Based on Tables 2 & 3\n3. -Threats to data. 2. Risk Analysis (RA)\n5. -Date of last RA. 6. -Person or contractor conducting RA. 7. -Methodology used. 8. -Action taken on recommendations. 9. -RA documentation. 3. Contingency Plans (CPs). 11. -Emergency response, back-up, and recovery for large systems\n12. -Status of plans. 13. -Documentation of CP. 14. -Used or tested (date)\n4. Description of Security Measures. - a. Physical Security. 17. -Locks, guards, detection systems. 18. -Fire and environmental hazards. - b. Personnel Security. 20. -Background investigations. 21. -Security clearances. - c. Administrative Procedures. 23. -Issuance of implementing security directives. 24."}], "metadata": {"source": "U.S. Department of Justice Simplified Risk Analysis 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 does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\n| 1. Introduction...................................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Fundamentals ................................................................................................................................4 |\n| 3. Measurement Considerations.......................................................................................................12 |\n| 3.1.1. Measures Documentation..........................................................................................................12 |\n| 3.1.2. Measurement Reporting ............................................................................................................14 |\n| 3.1.3. Data Management......................................................................................................................14 |\n| 3.1.4. Data Quality................................................................................................................................15 |\n| 3.1.5. Uncertainty and Errors ...............................................................................................................15 |\n| 3.3.1. Implementation Measures.........................................................................................................17 |\n| 3.3.2. Effectiveness Measures..............................................................................................................17 |\n| 3.3.3. Efficiency Measures....................................................................................................................18 |\n| 3.3.4."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "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 SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions provide? (Part 3)"}, {"role": "assistant", "content": ". Category of Standard : Computer Security Standard, Cryptography. 3. Explanation : This Standard (FIPS 202) specifies the Secure Hash Algorithm-3 (SHA-3) family of functions on binary data.\nEach of the SHA-3 functions is based on an instance of the KECCAK algorithm that NIST selected as the winner of the SHA-3 Cryptographic Hash Algorithm Competition. This Standard also specifies the KECCAKp family of mathematical permutations, including the permutation that underlies KECCAK, which can serve as the main components of additional cryptographic functions that may be specified in the future. The SHA-3 family consists of four cryptographic hash functions and two extendable-output functions (XOFs). The cryptographic hash functions are called SHA3-224, SHA3-256, SHA3384, and SHA3-512; and the XOFs are called SHAKE128 and SHAKE256. For hash functions, the input is called the message , and the output is called the (message) digest or the hash value . The length of the message can vary; the length of the digest is fixed. A cryptographic hash function is a hash function that is designed to provide special properties, including collision resistance and preimage resistance, that are important for many applications in information security. For example, a cryptographic hash function increases the security and efficiency of a digital signature scheme when the digest is digitally signed instead of the message itself. In this context, the collision resistance of the hash function provides assurance that the original message could not have been altered to a different message with the same hash value, and hence, the same signature. Other applications of cryptographic hash functions include pseudorandom bit generation, message authentication codes, and key derivation functions."}], "metadata": {"source": "SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Technical Guide to Information Security Testing and Assessment provide?"}, {"role": "assistant", "content": "\n\n## Technical Guide to Information Security Testing and Assessment\n\n## Recommendations of the National Institute of Standards and Technology\n\nKaren Scarfone Murugiah Souppaya Amanda Cody Angela Orebaugh\n\n## NIST Special Publication 800-115\n\nTechnical Guide to Information Security Testing and Assessment\n\nRecommendations of the National Institute of Standards and Technology\n\nKaren Scarfone Murugiah Souppaya Amanda Cody Angela Orebaugh\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nSeptember 2008\n\n\n\nU.S. Department of Commerce\n\nCarlos M. Gutierrez, Secretary\n\nNational Institute of Standards and Technology\n\nDr. Patrick D. Gallagher, Deputy Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology (IT). 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. National Institute of Standards and Technology Special Publication 800-115 Natl. Inst. Stand. Technol. Spec. Publ. 800-115, 80 pages (Sep."}], "metadata": {"source": "Technical Guide to Information Security Testing and Assessment", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\nsoftware at all times. Set it to automatically scan emails and flash drives. - o Continuously monitor directory services (and other primary user stores) for indicators of compromise or active attack.\n- o Block access to untrusted web resources. Use products or services that block access to server names, IP addresses, or ports and protocols that are known to be malicious or suspected to be indicators of malicious system activity. This includes using products and services that provide integrity protection for the domain component of addresses (e.g., hacker@poser.com)."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\n- a. National Organizations . As presented in Exhibit 1-1, the NASA Automated Information Security Program is based on public laws promulgated by Congress. The following organizations then issued national policies, standards, and guidelines:\n2. (1)\n3. The Department of Commerce (DOC)\n- (2) The National Institute for Standards and Technology (NIST)\n5. (3)\n6. The Office of Management and Budget (0MB)\n7. (4)\n8. (5)\n9. (6)\n10. The Office of Personnel Management (0PM)\n11. The National Security Agency (NSA)\n12. The Department of Defense (DOD)\n- (7) The General Services Administration (GSA)\n- (8) Various Presidential committees on computer and telecommunications systems security. - b. National Documents . National policy and guidance documents include:\n16. (1)\n17. (2)\n18. (3)\n19. Computer Security Act of 1987 (PL 100-235)\n20. Executive Order 12356. 21. 0MB Circular A-130. - (4) NIST Federal Information Processing Standards (FIPS) Publications. 23. (5)\n24. DOD guidance on protecting classified information. 25. (6)\n26. NSA guidance on trusted computer systems. - where multiple organizational levels or program area applications exist, Assistant PO-CSM*s and/or CSC*s may be designated to accomplish specific computer security responsibilities. - (3) Implement and coordinate an appropriate management oversight process that ensures awareness and compliance with applicable portions of NMI 2410.7 and this Handbook in cognizant organizations\n- (4) Assure that all NASA and appropriate NASA contractor computing and telecommunications resources processing NASA information are identified and included under the management of a DPI. - (5) Assure that, through the contracting officer, all appropriate contractors are required to comply with applicable provisions of NMI 2410.7 and this Handbook. - (6) Review and concur on exceptions from implementing specific requirements of this Handbook. - e. Other Headquarters Offices ."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "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 Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry:\n\nsecurity, and physical security increases with C-SCRM practice maturity. More mature companies have explicit roles that bridge these functions and also integrate them with enterprise risk management.\nSuch internal alignment facilitates the efficiency and effectiveness of delivering products and services while appropriately managing C-SCRM risks. For example, these integrated functions share information, metrics, and program objectives to reduce C-SCRM risks. This often results in a more nuanced and comprehensive understanding of cybersecurity risks by business executives, as well as better strategic decisions that take CSCRM into consideration."}], "metadata": {"source": "Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\n\n3.2.3. 3.2.3."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\nFederal CKMS service-using organizations should coordinate with their service-providing organization in defining and supporting security policies for providing key-management services for their users.\n|\n|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| PA:4.3 | A Federal CKMS service provider should have a Computer Security Policy. |\n| PA:4.4 | A Federal CKMS service-using organization should create a Computer Security Policy that identifies: a) The information that is processed, communicated, and stored within its computer systems that requires protection, b) The threats that are to be protected against, and c) The detailed rules for protecting the information by computers, communication systems, and computer users. |\n| PA:4.5 | A Federal CKMS should use and support applications using computer operating systems that provide security in accordance with the FCKMS service-using organization's Computer Security Policy. |"}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "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 Attribute-based Access Control for Microservices-based Applications using a Service Mesh:\n\nDeployment architecture in cloud-native applications now consists of loosely coupled components, called microservices, with all application services provided through a dedicated infrastructure, called a service mesh, independent of the application code. Two critical security requirements in this architecture are to build (1) the concept of zero trust by enabling mutual authentication in communication between any pair of services and (2) a robust access control mechanism based on an access control such as attribute-based access control (ABAC) that can be used to express a wide set of policies and is scalable in terms of user base, objects (resources), and deployment environment. This document provides deployment guidance for building an authentication and authorization framework within the service mesh that meets these requirements. A reference platform for hosting the microservices-based application and a reference platform for the service mesh are included to illustrate the concepts in the recommendations and provide the context in terms of the components used in real-world deployments.\n\nattribute-based access control; authentication policy; authorization policy; CI/CD; DevSecOps; JSON web token; microservices-based application; mutual TLS; next generation access control; policy enforcement point; role-based access control; service mesh; service proxy; zero trust.\n\nThe authors express their sincere thanks to Mr. David Ferraiolo of NIST for initiating this effort to provide a targeted deployment guidance in the form of an authentication and authorization framework in a service mesh environment used for protecting microservices-based applications. They also express thanks to Isabel Van Wyk of NIST for her detailed editorial review."}], "metadata": {"source": "Attribute-based Access Control for Microservices-based Applications using a Service Mesh", "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 Personnel Security?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n6.1 Special-Risk Security Provision. The U.S. Government has personnel, facilities, and other assets deployed and operating worldwide under a vast range of threats (e.g., terrorist, technical, intelligence), the severity of which is particularly heightened overseas. For cardholders with particularly sensitive threats while outside of the contiguous United States, the issuance, holding, and/or use of PIV credentials with full technical capabilities as described herein may result in unacceptably high risk. In such cases of risk (e.g., to facilities, individuals, operations, national interest, or national security) by the presence and/or use of full-capability PIV credentials, the head of a department or independent agency may issue a select number of maximum-security PIV credentials that do not contain (or otherwise do not fully support) the wireless and/or biometric capabilities otherwise required/referenced herein. To the greatest extent practicable, heads of departments and independent agencies should minimize the issuance of such special-risk security PIV credentials so as to support interagency interoperability and the President's policy. Use of other risk-mitigating technical (e.g., high-assurance on/off switches for the wireless capability) and procedural mechanisms in such situations is preferable and, as such, is also explicitly permitted and encouraged. As protective security technology advances, the need for this provision will be reassessed when the Standard undergoes the normal review and update process. Federal departments and agencies SHALL use the credentialing eligibility standards issued by the Director of the Office of Personnel Management (OPM) 3 and OMB."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Using Business Impact Analysis to Inform Risk Prioritization and Response provide? (Part 5)"}, {"role": "assistant", "content": "both federal and nonFederal Government corporate officers, high-level executives, ERM officers and staff members, and others who understand ERM but may be unfamiliar with the details of cybersecurity.\nAll readers are expected to gain an improved understanding of how CSRM and ERM complement and relate to each other as well as the benefits of integrating their use. ## 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. Cataloging and Categorizing Assets Based on Enterprise Value ........................................................6 |\n| 3."}], "metadata": {"source": "Using Business Impact Analysis to Inform Risk Prioritization and Response", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case provide?"}, {"role": "assistant", "content": "## NISTIR 8183A Volume 2\n\n## Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide:\n\nVolume 2 -Process-based Manufacturing System Use Case\n\nKeith Stouffer Timothy Zimmerman CheeYee Tang Jeffrey Cichonski Michael Pease Neeraj Shah Wesley Downard\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8183A-2\n\n\n\n## NISTIR 8183A Volume 2\n\n## Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide:\n\nVolume 2 -Process-based Manufacturing System Use Case\n\nKeith Stouffer Timothy Zimmerman CheeYee Tang Michael Pease Intelligent Systems Division Engineering Laboratory\n\nNeeraj Shah\n\nStrativia, LLC Largo, Maryland\n\nJeffrey Cichonski Applied Cybersecurity Division Information Technology Laboratory\n\nWesley Downard G2, Inc. Annapolis Junction, Maryland\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8183A-2\n\nSeptember 2019\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology\n\n## National Institute of Standards and Technology Internal Report 8183A, Volume 2 353 pages (September 2019)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8183A-2\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."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 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 does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\n| 4-4 |\n| 4.8 Security Standards for Multi-Vendor | Systems . . .\n.4-4 |\n| 4.9 Closing Thoughts | 4-5 |\n| LIST APPENDICES | APPENDIX A-1 |\n| APPENDIX APPENDIX A: LIST OF ORGANIZATIONS B: SAMPLING OF JOB TITLES | APPENDIX B-1 |\n| APPENDIX C: SAMPLE | QUESTIONS APPENDIX C-1 |\n| APPENDIX D: RELATED NIST ACTIVITIES AND | SOURCES OF INFORMATION APPENDIX D-1 |"}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Program Review for Information Security Management Assistance (PRISMA):\n\nMA Review is based upon the Software Engineering Institute's (SEI) former Capability Maturity Model (CMM), where an organization's developmental advancement is measured by one of five maturity levels.\nThis approach was incorporated into the Federal CIO Council's Federal Information Technology Security Assessment Framework of 2000 and PRISMA, which also employ five maturity levels where the fifth maturity level represents the highest developmental level of the information security program. The levels are listed in increasing maturity as follow:"}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\nThis report provides practical cybersecurity guidance for small-scale solar inverter implementations that are typically used in homes and small businesses. These guidelines are informed by a review of known smart-inverter vulnerabilities documented in the National Vulnerability Database (NVD), a review of information about known smart-inverter cyberattacks, and testing of five example smart inverters. The report also provides recommendations to smart-inverter manufacturers on the cybersecurity capabilities needed in their products to implement the seven guidelines. These recommendations build on the Internet of Things (IoT) cybersecurity capability baselines defined in NIST IR 8259A and IR 8259B by providing smartinverter-specific information for some of the baseline cybersecurity capabilities. Section 3 of this report provides ten cybersecurity capability recommendations for smartinverter manufacturers. These cybersecurity capabilities are derived from the Internet of Things cybersecurity capability core baselines presented in NIST Interagency Report (IR) 8259A and 8259B and enable implementation of the Sec. 2 guidelines. This report provides practical cybersecurity guidance for small-scale residential and lightcommercial inverters that are connected to the distribution network, not directly owned and operated by the utility, and typically used in homes and small businesses. It was developed by examining the current smart-inverter threat landscape, currently available smart-inverter cybersecurity capabilities, and potential mitigations that system installers, homeowners, and small business owners can implement. These capabilities and mitigations were validated through testing to demonstrate their practicality. The report provides recommendations to smart-inverter manufacturers for cybersecurity capabilities needed in their products to implement the seven guidelines."}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\n56 |\n| | 4.3.7. | De-Identifying Text Narratives and Qualitative Information . . . . . | 57 |\n| | 4.3.8.\n| Challenges Posed by Aggregation Techniques . . . . . . . . . . . . . | 57 |\n| | | 4.3.8.1. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 57 |\n| | 4.3.9. | Challenges Posed by High-Dimensional Data . . . . . . . . . . . . . | 58 |\n| | 4.3.10. | Challenges Posed by Linked Data . . . . . . . . . . . . . . . . . . . . | 59 |\n| | 4.3.11. | Challenges Posed by Composition . . . . . . . . . . . . . . . . . . . | 59 |\n| | 4.3.12. | Potential Failures of De-Identifcation . . . . . . . . . . . . . . . . . | 60 |\n| | 4.3.13. | Post-Release Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . | 61 |\n| 4.4. | Synthetic Data . . . . . . | . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 61 |\n| | 4.4.1. | Partially Synthetic Data . . . . . . . . . . . . . . . . . . . . . . . . . | 62 |\n| | 4.4.2. | Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 63 |\n| | 4.4.3. | Realistic Test Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 63 |\n| | 4.4.4. | Fully Synthetic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . | 63 |\n| | 4.4.5. | Synthetic Data with Validation . . . . . . . . . . . . . ."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "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 IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements provide? (Part 5)"}, {"role": "assistant", "content": "-53 Rev. 5 [800-53] controls implemented in systems. Just as not every Federal Information Technology (IT) system uses every control, not every capability in the catalog is needed in every IoT device.\nUltimately, the goal is to enable organizations to securely incorporate IoT devices into their systems and meet their security requirements. The catalog can be found in SP 800-213A, IoT Guidance for the Federal Government: IoT Device Cybersecurity Requirement Catalog [800-213A]. ## Acknowledgments\n\nThe authors wish to thank all contributors to this publication, including the participants in workshops and other interactive sessions; the individuals and organizations from the public and private sectors, including manufacturers from various sectors as well as several manufacturer trade organizations, who provided feedback on the preliminary public content; and colleagues at NIST who offered invaluable inputs and feedback. Special thanks to the NIST Risk Management Framework team for their extensive feedback. ## Audience\n\nThe target audience of this publication is information security professionals, system administrators, and others in organizations tasked with assessing, applying, and maintaining security on a system. ## 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."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop:\n\nes 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. ## 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 Email: 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\nThis report summarizes the feedback received on the work of the NIST Cybersecurity for IoT program on device cybersecurity at a virtual workshop in July 2020."}], "metadata": {"source": "Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment:\n\nIf appropriate, previous ISCM program assessment results may be reused as part of the information for the current ISCM program assessment (e.g., Inspector General reports, audits, vulnerability scans, physical security inspections, prior security or privacy assessments, developmental testing and evaluation, and vendor flaw remediation activities).\n\nA safeguard or countermeasure prescribed for an information system or an organization designed to protect the confidentiality, integrity, and availability of its information and to meet a set of defined security requirements."}], "metadata": {"source": "Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to U.S. Department of Energy Risk Assessment Methodology:\n\n|\n| C | RD FRD NSI | Q. L Q.TS.S, L Q.TS.S.L | 1,2, 5 1,2, 3, 4, 5, 1,2, 3, 4, 5, 6 |\n\n| d. MODES OF OPERATION: | d.\nMODES OF OPERATION: |\n|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| MODE | EXPLANATION |\n| SYSTEM HIGH SECURITY MODE | All system users in this enY-onment must possess dearances and authorizations for all information contained in the system, and ail system ou 5 )ut must be dearly marked with the highest dassification and all system caveats, until the information has been reviewed manually by an authorized individucti to ensure appropriate dassifications and caveats have been affixed."}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\n| 3.2 SWAM Sub-Capabilities and Defect Check Tables and Templates......................................27 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 3.2.1 Foundational Sub-Capabilities and Corresponding Defect Checks...............................28 | | 3.2.2 Data Quality Sub-Capabilities and Corresponding Defect Checks ...............................37 | | 3.2.3 Local Sub-Capabilities and Corresponding Defect Checks ...........................................45 | | 3.2.4 Security Impact of Each Sub-Capability on an Attack Step Model ................................74 | | 3.3 SWAM Control (Item) Security Assessment Plan Narrative Tables and Templates.............82 | | 3.3.1 Outline Followed for Each Control Item........................................................................83 | | 3.3.2 Outline Organized by Baselines......................................................................................83 | | 3.3.3 Low Baseline Security Control Item Narratives .............................................................85 | | 3.3.4 Moderate Baseline Security Control Item Narratives ..................................................115 | | 3.3.5 High Baseline Security Control Item Narratives..........................................................148 | | 3.4 Control Allocation Tables (CATs)......................................................................................165 | | 3.4.1 Low Baseline Control Allocation Table........................................................................166 | | 3.4.2 Moderate Baseline Control Allocation Table...............................................................168 | | 3.4.3 High Baseline Control Allocation Table.......................................................................169 | | Appendix A."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Program Review for Information Security Management Assistance (PRISMA):\n\n3.1.1 | Supporting Information for FISMA... 3.1.1 provides general assignment of information security responsibilities based on principles of separation of duties, least privilege and individual accountability. 3.1.1 | Does documented policy require employees and contractors to receive adequate training to fulfill their security responsibilities prior to access of the system? | Are procedures documented for employees and contractors to receive adequate training to fulfill their security responsibilities prior to access of the system? | Have employees and contractors received adequate training to fulfill their security responsibilities prior to access of the system? | Are employees' and contractors' understanding of their information and information system security responsibilities periodically assessed? | Is information and information system security an integral part of the duties of employees and contractors? |\n| Criterion 3."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Anonymous Renewable Energy Company:\n\n- Consolidate global regulatory requirements into common processes. Critical infrastructure operations invoke different compliance obligations from region to region. The Renewable Energy Company is consolidating these cybersecurity and supply chain obligations into a single set of requirements to be applied globally. This is expected to simplify compliance and supplier management while enhancing the company's global security posture. - Include access requirements when evaluating criticality. Traditional criticality assessments may not capture the full scope of a supplier's potential impact. Consider attack-surface factors, such as a supplier's access to information technology (IT) networks or physical facilities, to more accurately evaluate supplier criticality. - Limit unnecessary access to sensitive systems. Apply the principle of least privilege to acquired businesses and suppliers with access to Information Technology (IT)/Operational Technology (OT) networks. The Renewable Energy Company isolates newly acquired PV power plants until they replace existing systems with controlled, mature systems that can be safely integrated with the company's infrastructure. While many of the Renewable Energy Company's suppliers provide commodity products, the company relies on a small number of critical suppliers that provide complex digital components or specialized materials. The Renewable Energy Company considers two factors when determining a given supplier's criticality. First is the supplier's level of access to the company's network and facilities. For instance, an external robotics programmer would require physical access to the manufacturing floor and OT network and may require access to the larger IT network. The second factor to consider is the potential business impact of failure or compromise. The Renewable Energy Company prioritizes suppliers with high potential impacts on the power grid and proactively monitors them at the Security Operations Center."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Anonymous Renewable Energy Company", "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 Cybersecurity Framework Manufacturing 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": "Cybersecurity Framework Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\nquisition and implementation of IoT devices. This publication contains background and recommendations to help organizations consider how an IoT device they plan to acquire can integrate into a system.\nIoT devices and their support for security controls are presented in the context of organizational and system risk management. This publication provides guidance on considering system security from the device perspective. This allows for the identification of device cybersecurity requirements-the abilities and actions an organization will expect from an IoT device and its manufacturer and/or third parties, respectively."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "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 Key-Encapsulation Mechanisms provide? (Part 5)"}, {"role": "assistant", "content": ". . . . . . . . . . . . . . . . . . 1.1. Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Scope and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . .\n. . . . . . . 1.3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Overview of Key-Encapsulation Mechanisms . . . . . . . . . . . . . . . . . . . . . 2.1. Overview and Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2. Basic Definitions and Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. Theoretical Security of KEMs . . . . . . . . . . . . . . . . . . . . . . . . . . . 3. Requirements for Secure KEM Implementations . . . . . . . . . . . . . . . . . . . 3.1. Compliance With NIST Standards and Validation . . . . . . . . . . . . . . . . 3.2. Managing Cryptographic Data . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3. Additional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. Using KEMs Securely in Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1. How to Establish a Key With a KEM . . . . . . . . . . . . . . . . . . . . . . . 4.2. Conditions for Using KEMs Securely . . . . . . . . . . . . . . . . . . . . . . . 4.3. Post Processing of the Shared Secret Key . . . . . . . . . . . . . . . . . . . . 4.4. Key Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1. Creating the MAC Data . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.2. Obtaining the Key-Confirmation Key . . . . . . . . . . . . . . . . . . 4.4.3. Key-Confirmation Example . . . . . . . . . . . . . . . . . . . . . . . . 4.5. Proof of Possession for KEM Keys\n\n. . . . . . . . . . . . . . . . . . . . . . . . 4.6. Multi-Algorithm KEMs and PQ/T Hybrids . . . . . . . . . . . . . . . . . . . . 4.6.1. Constructing a Composite KEM . . . . . . . . . . . . . . . . . . . . . 4.6.2. Approved Key Combiners\n\n. . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Recommendations for Key-Encapsulation Mechanisms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Module-Lattice-Based Key-Encapsulation Mechanism Standard:\n\nNIST will continue to follow developments in the analysis of the ML-KEM algorithm. As with its other cryptographic algorithm standards, NIST will formally reevaluate this standard every five years."}], "metadata": {"source": "Module-Lattice-Based Key-Encapsulation Mechanism Standard", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\n3.1.2 Cyber Risk Management Strategy ... 3.1.2 Cyber Risk Management Strategy\n\nAn organization’s cyber risk management strategy (i. 3.1.2."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nThere may be references in this publication to other publications currently under\ndevelopment by NIST in accordance with its assigned statutory responsibilities. The\ninformation in this publication, including concepts and methodologies, may be used by\nfederal agencies even before the completion of such companion publications. Thus, until\neach publication is completed, current requirements, guidelines, and procedures, where\nthey exist, remain operative. For planning and transition purposes, federal agencies may\nwish to closely follow the development of these new publications by NIST. These guidelines cover the identity proofing, authentication, and federation of users\n(e.g., employees, contractors, or private individuals) who interact with government\ninformation systems over networks. They define technical requirements in each of\nthe areas of identity proofing, enrollment, authenticators, management processes,\nauthentication protocols, federation, and related assertions. They also offer technical\nrecommendations and other informative text as helpful suggestions. The guidelines are\nnot intended to constrain the development or use of standards outside of this purpose. This publication supersedes NIST Special Publication (SP) 800-63-3. The Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops\ntests, test methods, reference data, proof of concept implementations, and technical\nanalyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical,\nand physical standards and guidelines for the cost-effective security and privacy of other\nthan national security-related information in federal information systems."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n3.2.3 | Despliegue basado en un portal de recursos... 3.2.3), ya que la identidad y el estado del dispositivo proporcionan datos de referencia secundarios para las decisiones de acceso. 3.2.3 Despliegue basado en un portal de recursos\n\nEn este tipo de implementación, el PEP es un componente único que actúa como puerta de enlace para las solicitudes de los sujetos."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT):\n\nIoT cybersecurity objectives, risks, and threats are then analyzed for IoT applications in general and for each of the five illustrative IoT technology application areas. Cybersecurity objectives for traditional information technology (IT) systems generally prioritize Confidentiality, then Integrity, and lastly Availability. IoT systems cross multiple sectors as well as use cases within those sectors. Accordingly, cybersecurity objectives may be prioritized very differently by various parties, depending on the application. The increased ubiquity of IoT components and systems heighten the risks they present. Standards-based cybersecurity risk management will continue to be a major factor in the trustworthiness of IoT applications. Analysis of the\n\n1 Cybersecurity is defined as 'the prevention of damage to, unauthorized use of, exploitation of, and - if needed - the restoration of electronic information and communications systems, and the information they contain, in order to strengthen the confidentiality, integrity and availability of these systems' per NISTIR 8074 vol. 2\n\nThis report recognizes that cybersecurity-and cybersecurity standards- can support individuals' safety and privacy. For example, cybersecurity standards when applied to the confidentiality, integrity, or availability of personally identifiable information (PII) are an important component of protecting individuals' privacy. However, privacy cannot be achieved solely by securing individuals' PII (see Figure 1). As noted in NISTIR 8062, An Introduction to Privacy Engineering and Risk Management in Federal Systems, privacy concerns can arise from intentional or authorized processing of information about individuals, and in certain contexts, even measures used to secure PII can result in privacy issues [8]."}], "metadata": {"source": "Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\n\n3.3.1."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "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 guidance does Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities provide?"}, {"role": "assistant", "content": "\n\nSpecial Publication 800-84 Sponsored by the Department of Homeland Security\n\n## Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities\n\n## Recommendations of the National Institute of Standards and Technology\n\nTim Grance Tamara Nolan Kristin Burke Rich Dudley Gregory White Travis Good\n\n## NIST Special Publication 800-84\n\nGuide to Test, Training, and Exercise Programs for IT Plans and Capabilities\n\nRecommendations of the National Institute of Standards and Technology\n\nTim Grance, Tamara Nolan, Kristin Burke, Rich Dudley, Gregory White, Travis Good\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nSeptember 2006\n\n\n\n## U.S. Department of Commerce\n\nCarlos M. Gutierrez, Secretary\n\n## Technology Administration\n\nRobert C. Cresanti, Under Secretary of Commerce for Technology\n\nNational Institute of Standards and Technology\n\nWilliam A. Jeffrey, Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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."}], "metadata": {"source": "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Fiscal Year 2022 Cybersecurity and Privacy Annual Report:\n\nThis past year, NIST conducted research and demonstrated practical applications in several key priority areas, including Post Quantum Cryptography (and the selection of PQC algorithms for standardization); an update to the NIST Cybersecurity Framework (CSF 2.0), including new CSF profiles; software and supply chain cybersecurity; our Internet of Things (IoT) cybersecurity guidelines work; launching a new comment site for our security and privacy controls and baselines (so we can get our resources into the hands of practitioners faster and improve the user experience for our customers); and much more. - NIST kicked off the Journey to CSF 2.0 with a Request for Information (RFI), a summary analysis document of the RFI responses, and a workshop with 3,900+ attendees from 100 countries. More planning is now underway for additional workshops and drafts. - Updated guidance on assessing security and privacy controls was released, featuring updated assessment procedures to better enable automation. - Guidance on managing cybersecurity risk in supply chains for all levels of an organization was released with specific sections focused on securing software supply chains. Additionally, NIST collaborated with software developers, service providers, and users to develop secure software development guidance that is now mandatory for federal agency software acquisition and use. - New guidance and example implementations were developed and released to demonstrate how organizations can verify that the internal components of their computing devices are genuine and have not been tampered with. - NIST published guidance to enhance and strengthen the security and integrity of the software supply chain in support of Executive Order (EO)14028. This effort included cybersecurity supply chain risk management practices and guidelines for software developer verification, systems security engineering, and secure software development."}], "metadata": {"source": "Fiscal Year 2022 Cybersecurity and Privacy Annual Report", "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 PBX Administrator’s Security Standards:\n\n| Policy | |\n|-----------------------------------------|----------|\n| Section 1: FDIC Telephone | |\n| FDIC Telephone Usage Policy | 1-1 |\n| PBX Protection Policy | 1-1 |\n| Acquisition Policy | 1-1 |\n| Security Incident Reporting Policy | 1-1 |\n| Typical Telephone System Configurations | 1-2 |\n| Terms Used in GS/SYS85 and G1/SYS75 | 1-3 |\n| Section 2: PBX Fraud | |\n| PBX Fraud History | 2-1 |\n| Illegally Obtaining Authorization Codes | 2-2 |\n| Observation | 2-2 |\n| Social Engineering Schemes | 2-2 |\n| Operator Direct Dial Scheme | 2-2 |\n| Call/Sell Operations | 2-3 |\n| Call Diverter Schemes | 2-3 |\n| Remote Access Fraud | 2-3 |\n| Voice Mail Fraud | ."}], "metadata": {"source": "PBX Administrator’s Security Standards", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Information System Security Best Practices for UOCAVA-Supporting Systems:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by organizations 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, organizations may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Information System Security Best Practices for UOCAVA-Supporting 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 Awareness and Training?"}, {"role": "assistant", "content": "According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\n| Function Unique Identifier | Function | Category Unique Identifier | Category | |------------------------------|---------------|------------------------------|---------------------------------------------------------| | ID-P | Identify-P | ID.IM-P | Inventory and Mapping | | ID-P | Identify-P | ID.BE-P | Business Environment | | ID-P | Identify-P | ID.RA-P | Risk Assessment | | ID-P | Identify-P | ID.DE-P | Data Processing Ecosystem Risk Management | | GV-P | Govern-P | GV.PO-P | Governance Policies, Processes, and Procedures | | GV-P | Govern-P | GV.RM-P | Risk Management Strategy | | GV-P | Govern-P | GV.AT-P | Awareness and Training | | GV-P | Govern-P | GV.MT-P | Monitoring and Review | | CT-P | Control-P | CT.PO-P | Data Processing Policies, Processes, and Procedures | | CT-P | Control-P | CT.DM-P | Data Processing Management | | CT-P | Control-P | CT.DP-P | Disassociated Processing | | CM-P | Communicate-P | CM.PO-P | Communication Policies, Processes, and Procedures | | CM-P | Communicate-P | CM.AW-P | Data Processing Awareness | | PR-P | Protect-P | PR.PO-P | Data Protection Policies, Processes, and Procedures | | PR-P | Protect-P | PR.AC-P | Identity Management, Authentication, and Access Control | | PR-P | Protect-P | PR.DS-P | Data Security"}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters:\n\n| 4.2 General Issues ........................................................................33 | 4.2 General Issues ........................................................................33 | 4.2 General Issues ........................................................................33 | | |-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|----| | 4.2.1 | 4.2.1 | Voter Identification and Authentication..................................33 | | | 4.2.2 | 4.2.2 | Ballot Accounting ...............................................................34 | | | 4.2.3 | 4.2.3 | Return Identification...........................................................35 | | | 4.2.4 | 4.2.4 | Ballot Tracking...................................................................35 | | | 4.2.5 | 4.2.5 | Ballot Preparation...............................................................36 | | | 4.3 | Fax Transmission.....................................................................37 | Fax Transmission.....................................................................37 | | | 4.4 | Electronic Mail.........................................................................38 | Electronic Mail.........................................................................38 | | | 4.5 | Web-Based File Repositories......................................................39 | Web-Based File Repositories......................................................39 | | | 4.6 | Online Ballot Markers ...............................................................39 | Online Ballot Markers ...............................................................39 | | | 5 OTHER RESOURCES...................................................................."}], "metadata": {"source": "Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Anonymous Consumer Goods Company:\n\nThe Consumer Goods Company uses contractual requirements consistent with data privacy regulations and the NIST Cybersecurity Framework i (NIST CSF) as the key means for managing cyber supply chain risks. New suppliers are required to have cyber insurance and provide assurance that contractual cybersecurity controls have been met. While these requirements are present in all baseline supplier contracts, the company is sensitive to unique supplier capabilities and may accept alternative mitigating controls if they do not introduce unacceptable risk. Commercial sourcing handles contract negotiations, and the CISO's organization and legal review proposed amendments to ensure relevant risks are appropriately addressed. However, the company will not consider amending compliance-related requirements. All suppliers must demonstrate conformance with relevant data privacy laws, such as the European Union's General Data Protection Regulation (GDPR)."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Anonymous Consumer Goods Company", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management:\n\n3.2.1. 3.2.1 Improving Estimation Based on Knowledge of Prior Events\n\nInformation about previous risk events may be helpful when estimating the likelihood and impact of those in the future."}], "metadata": {"source": "Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Physical Protection?"}, {"role": "assistant", "content": "According to 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 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\n## Guideline #1: Change Default Passwords and Credentials\n\nDevice manufacturers often create preconfigured accounts that may have well-known or easilydiscoverable default passwords, individual device-specific passwords, or other access credentials to simplify the installation and setup of a device. However, once installed and\n\nconnected to communication networks, these passwords and credentials may allow anyone who knows the values to access the device and change its configuration."}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\nISA/IEC 62443 , Security for Industrial Automation and Control Systems (IACS) [15], is a collection of standards that address the requirements and methods for managing the cybersecurity of control systems and operational technology. The standards are organized in four layers: general, policy and procedures, system, and component. ISA-62443-2-1 defines requirements for security programs that consist of implementing and maintaining procedural, personnel, and"}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to An Introduction to Information Security:\n\n|\n| 7.1 Authorization ...................................................................................................\n| 38 |\n| 7.1.1 Authorization and Assurance..............................................................39 7.1.2 Authorization of Products to | Operate in Similar Situation...................39 |\n| 7.2 Security Engineering....................................................................................... | 39 |\n| 7.2.1 Planning and Assurance.....................................................................39 | |\n| 7.2.2 Design and Implementation Assurance..............................................39 | |\n| 7.3 Operational Assurance...................................................................................."}], "metadata": {"source": "An Introduction to Information 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 is CMMC practice AC.L2-3.1.12 (NIST 3.1.12)?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\n3.1.12 Verify signature algorithm in SignerInfo\n\n| Purpose | Confirms that the signatureAlgorithm field specified in the SignerInfo ordance with Table 3-4 of SP80078 and based on the PIV card field is in acc expiration date in accordance with Table 3-3 of SP80078. 3.1.12: Verify signatu algorithm in SignerInfo re | mis in The tester shall validate that the signature algorith based on the expiration date of the PIV card and is accordance with Table 3-4 of SP 800-78."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "nist_control": "3.1.12", "cmmc_practice_id": "AC.L2-3.1.12", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Program Review for Information Security Management Assistance (PRISMA):\n\n3.1.4 | Information Security Program Benchmark... 3.1.4 | … | … | … | … | … |\n| Aggregate Scores >>> | Compliant | Partially Compliant | Partially Compliant | Partially Compliant | Noncompliant |\n\nTable 2-9, Scorecard Representation of Table 2-8 above\n\n\n\n| | Maturity Level Evaluation Questions | Maturity Level Evaluation Questions | Maturity Level Evaluation Questions | Maturity Level Evaluation Questions | Maturity Level Evaluation Questions |\n|-----------|---------------------------------------|---------------------------------------|---------------------------------------|---------------------------------------|---------------------------------------|\n| | Policy | Procedures | Implementation | Test | Criteria Integration |\n| Compliant | Compliant | Partially Compliant | Partially Compliant | Noncompliant | Criterion 3. 3.1.4 |\n| Compliant | Partially Compliant | Partially Compliant | Partially Compliant | Noncompliant | Aggregate Scores >>> |\n\nTable 2-10 below presents the PRISMA scores of STA 3."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.7 (NIST 3.5.7)?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\n3.5.7 Information Management Information Type... 3.5.7, Information Management Information. 3.5.7 Information Management Information Type\n\nInformation Management involves the coordination of information collection, storage, and dissemination, and destruction as well as managing the policies, guidelines, and standards regarding information management."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "cmmc_level": "all", "nist_control": "3.5.7", "cmmc_practice_id": "IA.L2-3.5.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guide for Cybersecurity Event Recovery:\n\ncuring applications and services, changing passwords, increasing the intensity of monitoring, and tightening network perimeter security (e.g., firewall rulesets, boundary router access control lists).\nProcedures may also include non-technical actions that involve changes to business\n\n- The recovery continues to support the various communication teams as they interact with internal users and public customers. - The recovery teams close the loop with the external entities such as law enforcement and information sharing organizations who have been involved during the tactical phase. - A plan is developed to include longer-term goals that have to be met to fully correct the root causes. Some of these improvements include implementing stronger authentication mechanisms, isolating administrative processes from general productivity activities, implementing least privilege principle, using encryption to protect customers' data, and deploying better monitoring capabilities. The team makes long-term recommendations which include first to fully discover and identify sensitive data, in particular personally identifiable data, intellectual property data, and financial data across the entire organization including external hosted services. Second, a data loss prevention technology can be implemented to prevent future leakage of sensitive data by providing visibility and control of the data across the IT infrastructure, in particular at the endpoints, data stores, and gateways of the organization. Finally, the organization needs to develop a policy and process to implement this strategy successfully. These actions will involve vetting and approval from the management, business units, and IT teams, as they will include"}], "metadata": {"source": "Guide for Cybersecurity Event Recovery", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide to Protecting the Confidentiality of Personally Identifiable Information (PII):\n\n7 Disposal of PII should be conducted in accordance with the retention schedules approved by the National Archives and Records Administration (NARA), as well as in accordance with agency litigation holds.\n\nOrganizations are required to identify all PII residing within their organization or under the control of their organization through a third party (e.g., a system being developed and tested by a contractor). Organizations should use a variety of methods to identify PII. Privacy threshold analyses (PTAs), also referred to as initial privacy assessments (IPAs), are often used to identify PII. 19 Some organizations require a PTA to be completed before the development or acquisition of a new information system and when a substantial change is made to an existing system. PTAs are used to determine if a system contains PII, whether a Privacy Impact Assessment (PIA) is required, whether a System of Records Notice (SORN) is required, and if any other privacy requirements apply to the information system. PTAs are usually submitted to an organization's privacy office for review and approval. PTAs are comprised of simple questionnaires that are completed by the system owner in collaboration with the data owner. PTAs are useful in initiating the communication and collaboration for each system between the privacy officer, the information security officer, and the information officer. Other examples of methods to identify PII include reviewing system documentation, conducting interviews, conducting data calls, using data loss prevention technologies (e.g., automated PII network monitoring tools), or checking with system and data owners. Organizations should also ensure that retired hardware no longer contains PII and that proper sanitization techniques are applied. 20\n\n20 For more information on media sanitization, see NIST SP 800-88, Guidelines for Media Sanitization , http://csrc.nist.gov/publications/nistpubs/800-88/NISTSP800-88\\_rev1.pdf."}], "metadata": {"source": "Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)", "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 Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance:\n\n1. The system administrator shall ensure that the organization's security policy is enforced.\n2. Key recovery procedures shall be in place to ensure that users can recover their data if they lose their authentication information (password, token data, etc). A method for data recovery personnel to authenticate these users should be in place prior to the recovery of the user's keys or files.\n3. If the EFS includes a master administrator password for use in data recovery by the system administrator, the system administrator shall utilize a strong password.\n4. System administrators shall provide training and security guidance to the end users of the system that, at a minimum, focuses on passwords, data-recovery procedures, and user configuration of their system to utilize the authentication features within the system."}], "metadata": {"source": "Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance", "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Managing Information Security Risk_ Organization, Mission, and Information System View:\n\n3 While federal agencies are required to follow certain specific NIST Special Publications in accordance with OMB policy, there is flexibility in how agencies apply the guidance. Federal agencies apply the security concepts and principles articulated in the NIST Special Publications in accordance with and in the context of the agency's missions, business functions, and environment of operation. Consequently, the application of NIST guidance by federal 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. Given the high priority of information sharing and transparency within the federal government, agencies also consider reciprocity in developing their information security solutions. When assessing federal agency compliance with NIST Special Publications, Inspectors General, evaluators, auditors, and assessors consider the intent of the security concepts and principles articulated within the specific guidance document and how the agency applied the guidance in the context of its mission/business responsibilities, operational environment, and unique organizational conditions. - Assignment of risk management responsibilities to senior leaders/executives;\n- Ongoing recognition and understanding by senior leaders/executives of the information security risks to organizational operations and assets, individuals, other organizations, and the Nation arising from the operation and use of information systems;\n- Establishing the organizational tolerance for risk and communicating the risk tolerance throughout the organization including guidance on how risk tolerance impacts ongoing decision-making activities; 8 and\n- Accountability by senior leaders/executives for their risk management decisions and for the implementation of effective, organization-wide risk management programs."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "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 Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\n- Functions organize basic cybersecurity activities at their highest level. These Functions are Identify, Protect, Detect, Respond, and Recover. They aid an organization in expressing its management of cybersecurity risk by organizing information, enabling risk management decisions, addressing threats, and improving by learning from previous activities. The Functions also align with existing methodologies for incident management and help show the impact of investments in cybersecurity. For example, investments in planning and exercises support timely response and recovery actions, resulting in reduced impact to the delivery of services.\n- Categories are the subdivisions of a Function into groups of cybersecurity outcomes closely tied to programmatic needs and particular activities. Examples of Categories include 'Asset Management,' 'Access Control,' and 'Detection Processes.'\n\nThe Protect Function supports the ability to limit or contain the impact of a potential cybersecurity event. Examples of outcome Categories within this Function include: Access Control; Awareness and Training; Data Security; Information Protection Processes and Procedures; Maintenance; and Protective Technology.\n\n- Steps are taken to identify and address the privacy implications of access control measures to the extent that they involve collection, disclosure, or use of personal information"}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "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 PBX Administrator’s Security Standards provide? (Part 3)"}, {"role": "assistant", "content": "i''''\n\ni?0\n\nYf-.iF\n\naX. •.-<\n\n'S' f\n\n^^'. f\n\n•>•'\n\n'i\n\n'7.i'''\n\n< T*'*\n\nv'itO'.t:\n\n(1^3 J'\n\nCjlti/'fif'Jf't^!5'f!tX'\n\n'\n\nAa.u,Ti^^ t^^'. (ig'Ot)'. .i\n\n. .1,\n\n^\n\n... /\n\n•«. ^^'\n\n7'\n\n'•'\n\n'\n\n..\n;\n\n,,\n\n'7-;^;;r..;|i,\n\nIS'\n\n\n\n## PBX Administrator's Security Standards\n\n\n\n| Policy | |\n|-----------------------------------------|----------|\n| Section 1: FDIC Telephone | |\n| FDIC Telephone Usage Policy | 1-1 |\n| PBX Protection Policy | 1-1 |\n| Acquisition Policy | 1-1 |\n| Security Incident Reporting Policy | 1-1 |\n| Typical Telephone System Configurations | 1-2 |\n| Terms Used in GS/SYS85 and G1/SYS75 | 1-3 |\n| Section 2: PBX Fraud | |\n| PBX Fraud History | 2-1 |\n| Illegally Obtaining Authorization Codes | 2-2 |\n| Observation | 2-2 |\n| Social Engineering Schemes | 2-2 |\n| Operator Direct Dial Scheme | 2-2 |\n| Call/Sell Operations | 2-3 |\n| Call Diverter Schemes | 2-3 |\n| Remote Access Fraud | 2-3 |\n| Voice Mail Fraud | ."}], "metadata": {"source": "PBX Administrator’s Security Standards", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Recommendation for Existing Application-Specific Key Derivation Functions:\n\n3.2.1 and 4."}], "metadata": {"source": "Recommendation for Existing Application-Specific Key Derivation Functions", "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 is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Guide to Information Technology Security Services:\n\n3.1.3. 3.1.3 Review Management Procedures and Controls-Program Assessment\n\nThe Contractor shall examine the management procedures that support security."}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nSome of the threats to wireless IMDs include device reprogramming, data extraction, data tampering, repeated access attempts and data flooding. Vulnerabilities include unsecured communication channels, inadequate authentication and access control, weak audit mechanisms and meager storage. The resulting risks include patient safety compromise resulting from firmware malfunction or therapy misconfiguration, device unavailability due to battery power depletion, patient privacy loss due to data leakage to unauthorized parties, and inappropriate medical follow-up due to tampering of patient readings. While some cyber threats may be unintentional, various motivations exist for deliberate cyber attacks, such as patient information gathering, negative impact to patient health status, ego satisfaction of the attacker, as well as gaining competitive advantage over another vendor through negative press. ## C. Authentication and Access Control Mechanisms\n\nFor each type of data identified, the authentication and access control mechanisms applicable for extracting or updating the data type need to be reviewed to determine adequacy of the protection mechanisms while balancing the needs of patient safety in emergency situations and the utility of the IMD within a patient's environment. This is a non-trivial exercise since the security and privacy requirements for IMDs frequently conflict with the requirements stemming from emergency access to patient data and device utility in hospital and home settings. Creative approaches may be devised to decouple data essential for patient safety in emergency conditions from patient personally identifiable information/data to allow different authentication and access control mechanisms to apply to each group of data."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements provide? (Part 4)"}, {"role": "assistant", "content": "roducts and modules need in order to be eligible for an SCAP validation. Government agencies and integrators use the information to gain insight into the criteria required for SCAP validated products.\nThe secondary audience for this publication includes end users, who can review the test requirements in order to understand the capabilities of SCAP validated products and gain knowledge about SCAP validation. ## Trademark Information\n\nOVAL and CVE are registered trademarks, and CCE, CPE, and OCIL are trademarks of The MITRE Corporation. Red Hat is a registered trademark of Red Hat, Inc. Windows operating system is registered trademark of Microsoft Corporation. All other registered trademarks or trademarks belong to their respective organizations. ## Summary of Changes\n\nThe following table details the changes between NISTIR 7511 Revision 3 and NISTIR 7511 Revision 4, which are incorporated in the present document."}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio:\n\non every time an Informative Reference is added or updated, Informative References are omitted from this publication. Instead, they will be held in NIST's Online Informative References (OLIR) Catalog.\n| Category | Subcategory | Implementation Example |\n|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | MA-RR-5 : Risk responses that will take an extended period of time or require additional funding to fully enact are recorded and tracked. | A federal agency determines that a risk will take two years to fully address and records the corresponding risk plan in a Plan of Action& Milestones (POA&M) document."}], "metadata": {"source": "Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nMany U.S. Government Information Technology (IT) systems need to employ strong cryptographic schemes to protect the integrity and confidentiality of the data that they process. Algorithms such as the Advanced Encryption Standard (AES), as defined in Federal Information Processing Standard (FIPS) 197, 1 and HMAC, as defined in FIPS 198, 2 make attractive choices for the provision of these services. These algorithms have been standardized to facilitate interoperability between systems. However, the use of these algorithms requires the establishment of secret keying material that is shared in advance. Trusted couriers may manually distribute this secret keying material, but as the number of entities using a system grows, the work involved in the distribution of the secret keying material grows rapidly. Therefore, it is essential to support the cryptographic algorithms used in modern U.S. Government applications with automated keyestablishment schemes. | Additional input | Information known by two parties that is cryptographically bound to the secret keying material being protected using the encryption operation."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Small Business Information Security_ The Fundamentals:\n\n| WHY SMALL BUSINESSES?\n.............................................................................................................4 | |\n| | 1.2 | ORGANIZATION OF THIS PUBLICATION..............................................................................................5 | |\n| 2 | UNDERSTANDING AND MANAGING YOUR RISKS .................................................................................... | UNDERSTANDING AND MANAGING YOUR RISKS ...................................................................................."}], "metadata": {"source": "Small Business Information Security_ The Fundamentals", "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 Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities provide? (Part 2)"}, {"role": "assistant", "content": "is 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.\nNational Institute of Standards and Technology Special Publication 800-84 Natl. Inst. Stand. Technol. Spec. Publ. 800-84, 97 pages (September 2006)\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 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. ## Acknowledgements\n\nThe authors, Tim Grance of the National Institute of Standards and Technology (NIST); Tamara Nolan, Kristin Burke, and Rich Dudley of Booz Allen Hamilton; and Dr. Gregory White and Travis Good of the University of Texas-San Antonio (UTSA); wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. The authors would like to acknowledge Joan Hash, Karen Kent, Peter Mell, Matt Scholl, Marianne Swanson, and Mark Wilson of NIST; Dick Broome, Kara Crawley, Courtney Hawkins, Munir Majdalawieh, and Zara Pyatt of Booz Allen Hamilton; and Dwayne Williams of UTSA for their keen and insightful assistance throughout the development of the document. The authors would also like to express their thanks to Glenn Fiedelholtz, Annabelle Lee, and Jeffrey Wright from the National Cyber Security Division of the Department of Homeland Security, as well as representatives from the Department of State and the MITRE Corporation, for their valuable comments and suggestions. The National Institute of Standards and Technology would also like to express its appreciation and thanks to the Department of Homeland Security for its sponsorship and support of NIST Special Publication 80084."}], "metadata": {"source": "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Cyber Threat Information Sharing provide? (Part 5)"}, {"role": "assistant", "content": "ication and distribution of threat information, engage with existing sharing communities, and make effective use of threat information in support of the organization's overall cybersecurity practices.\n## Keywords\n\ncyber threat; cyber threat information sharing; indicators; information security; information sharing\n\n## Acknowledgments\n\nThe authors, Chris Johnson, Lee Badger, and David Waltermire of the National Institute of Standards and Technology (NIST), and Julie Snyder and Clem Skorupka of The MITRE Corporation, wish to thank their colleagues who contributed to this publication, including Tom Millar and Rich Struse of the Department of Homeland Security (DHS); Karen Quigg, Richard Murad, Carlos Blazquez, and Jon Baker of The MITRE Corporation; Murugiah Souppaya and Melanie Cook of NIST; Ryan Meeuf, of the Software Engineering Institute, Carnegie Mellon University; George Saylor, Greg Witte, and Matt Smith of G2 Inc.; Karen Scarfone of Scarfone Cybersecurity; Chris Bean of the National Security Agency (NSA); Eric Burger of the Georgetown Center for Secure Communications, Georgetown University; Joe Drissel of Cyber Engineering Services Inc.; Tony Sager of the Center for Internet Security; Kent Landfield of Intel Security; Bruce Potter of KEYW Inc.; Jeff Carpenter of Dell SecureWorks; Ben Miller of the North American Electric Reliability Corporation (NERC); Anton Chuvakin of Gartner, Inc.; Johannes Ullrich of the SANS Technology Institute; Patrick Dempsey, Defense Industrial Base Collaborative Information Sharing Environment (DCISE); Matthew Schuster, Mass Insight; Garrett Schubert of EMC; James Caulfield of the Federal Reserve; Bob Guay of Biogen; and Chris Sullivan of Courion. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs:\n\nTo improve the security of enterprise networks, it is necessary to measure the amount of security provided by different network configurations. The objective of our research was to develop a standard model for measuring security of computer networks. A standard model will enable us to answer questions such as 'Are we more secure than yesterday?' or 'How does the security of one network configuration compare with another?' Also, having a standard model to measure network security will bring together users, vendors, and researchers to evaluate methodologies and products for network security.\n\nAs an example, consider Figure 1. The left side shows a network configuration, and the right side shows the attack graph for compromise of the database server by a malicious workstation user. In the network configuration, the firewall is intended to help protect the internal network. The internal file server offers file transfer (ftp), secure shell (ssh), and remote shell (rsh) services. The internal database server offers ftp and rsh services. The firewall allows ftp, ssh, and rsh traffic from a user workstation to both servers, and blocks all other traffic.\n\nIn [31] [32], a network security analyzer based on Datalog is described. The information in vulnerability databases, the configuration information for each machine, and other relevant information are all encoded as Datalog facts. The reasoning engine captures the interaction among various components in the network. The reasoning engine in MULVAL scales well (O(n 2 )) with the size of the network."}], "metadata": {"source": "Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs", "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 Security Guidelines for Storage Infrastructure:\n\nThe physical intrusion can involve 'overt access' in which the attacker will masquerade as someone who belongs in the situation (e.g., by playing the part of a cleaning employee, technician, or building maintenance personnel).\n\n- (d) For sensitive data, a comprehensive inventory of storage media (cataloging) should be kept, to track its location, ownership, capacity, and other relevant configuration attributes. Particular attention should be paid to tracking the actual content of media, including:\n- Sensitivity level,\n- Classification (what type of data it stores, what applications and business services it relates to),\n- Encryption level,\n- Potential impact if compromised or stolen (e.g., compromise of financial or medical information; leakage of passwords, certificates, or encryption keys).\n- Mitigation/contingency steps or procedures to employ (e.g., changing passwords, reissuing keys, re-encrypting data, and notifying relevant stake holders).\n- Dependencies between the data and other application.\n- (e) Consider using advanced tracking controls on sensitive removable media, such as RadioFrequency Identification (RFID) tags, Global Positioning System (GPS) tracking devices and tamper protection.\n- (f) For extremely sensitive information consider the use of self-activated and/or remotely controlled self-destruction mechanism. When implemented, carefully consider how to protect such capabilities as they present an attack vector an adversary could use to trigger destruction of the devices, or to harm nearby equipment, data and personnel."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Security Architecture Design Process for Health Information Exchanges (HIEs):\n\nd and incorporated. - 2) Enabling Services: Enabling Services define the nomenclature of services required to implement Capstone Policies. Enabling Services are designed to be HIE context-independent.\nServices presented in this publication are derived from common industry-wide data protection practices and then customized to specifically address the requirements of HIEs. - 3) Enabling Processes: Enabling Processes define the operational baseline via use cases and scenarios for Enabling Services. Enabling Processes are HIE context-dependent. Two HIEs could, for example, have different Enabling Processes implementing the same Enabling Service (e.g., 'Access Control'). - 4) Notional Architectures: Notional Architectures define the technical constructs (e.g., rolebased access control and directory services) and their relationships to implement Enabling Processes. The Notional Architecture is the blueprint to drive the selection of technical solutions and data standards. The Notional Architecture is standards-based, technologyneutral, and vendor-neutral. - 5) Technology Solutions and Standards: Technical solutions and data standards represent the selected technical solutions and data standards needed to implement the Notional Architecture."}], "metadata": {"source": "Security Architecture Design Process for Health Information Exchanges (HIEs)", "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 A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\n| PR:4.5 | PL-1 | A Federal CKMS shall make its FCKMS Security Policy available to all its FCKMS service-using organizations and their authorized users. |\n|----------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| PR:4.6 | AT-2 | Federal CKMS users and managers shall receive training about the security policies relevant to the FCKMS and the use of the FCKMS in accordance with those policies."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "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 Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity provide? (Part 5)"}, {"role": "assistant", "content": "ruptive events [to critical infrastructure]. The effectiveness of a resilient infrastructure or\n\n1 Information technology (IT) means: 'The art and applied sciences that deal with data and information.\nExamples are capture, representation, processing, security, transfer, interchange, presentation, management, organization, storage, and retrieval of data and information.' ( American National Standard Dictionary of Information Technology (ANSDIT) , available at http://www.incits.org/standardsinformation/ [accessed 11/20/2015].)\n\n2 ' Industrial control system (ICS) is a general term that encompasses several types of control systems, including supervisory control and data acquisition (SCADA) systems, distributed control systems (DCS), and other control system configurations such as Programmable Logic Controllers (PLC) often found in the industrial sectors and critical infrastructures.' (NIST Special Publication 800-82 Revision 2 Guide to Industrial Control Systems (ICS) Security , May 2015, p. 2-1. http://dx.doi.org/10.6028/NIST.SP.800-82r2.)\n\n3 U.S. Department of Homeland Security, Blueprint for a Secure Cyber Future: the Cybersecurity Strategy for the Homeland Security Enterprise , November 2011, p. D-2. Available at: http://www.dhs.gov/xlibrary/assets/nppd/blueprint-for-a-secure-cyber-future.pdf [accessed 11/20/2015]. ## NISTIR 8074 Volume 1\n\nenterprise depends upon its ability to anticipate, absorb, adapt to, and/or rapidly recover from a potentially disruptive event.' 4\n\nCybersecurity relies upon a diverse set of standards including standards whose scopes are specific to one or more attributes of cybersecurity and standards from other domains that are relevant to cybersecurity. The U.S. standardization community is comprised largely of non-governmental Standards Developing Organizations (SDOs). These groups are primarily shaped by industry (both U.S."}], "metadata": {"source": "Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Risk Management for Replication Devices:\n\n-  Default administration/configuration password: Many devices have default passwords which can be easily obtained and used to access configuration panels, stored data, or to control the device locally or remotely via a web interface. -  Data capture: When data is transmitted or stored unencrypted, it is subject to interception. This data may include device passwords, configuration settings, or processed jobs. Such data may appear to be unreadable but is an exploitable vulnerability if it is not encrypted. -  Disruption of service: RDs may be susceptible to a variety of threats which disrupt the availability of services. User interfaces, power consumption, and internal mechanical and software operations may be especially vulnerable. -  Spam: Most RDs, if not properly configured, will process any submitted job, without regard to the originator, without confirmation that the job is authorized, and without authentication. If exploited, this vulnerability may waste ink, paper, toner, or other materials while also resulting in a denial of service for legitimate users. -  Alteration/corruption of data: Exploits of this nature may be very difficult to detect, but could result in reduced quality, a denial of service (for example, if a password is altered), or a potentially hazardous situation (for example, if configuration settings are altered to allow the device to overheat). -  Outdated and/or unpatched operating systems and firmware: Many RDs run an embedded commercial operating system which renders them subject to the same threats and vulnerabilities as any other computing device running those same operating systems. To complicate matters, RD manufacturers may embed versions of operating systems for which the operating system provider is no longer providing updates or the functionality to install patches or updates is not available."}], "metadata": {"source": "Risk Management for Replication Devices", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 Personnel Security?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\nDe-Identifcation . . . . . | 18 |\n| 3.2. | Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n| Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| | 3.2.1. | Probability of Re-Identifcation . . . . | 21 |\n| | | 3.2.2. Adverse Impacts of Re-Identifcation . | 24 |\n| | | 3.2.3. Impacts Other Than Re-Identifcation | 26 |\n| | | 3.2.4. Remediation . . . . . . . . . . . . . . . | 27 |\n| | | Data Life Cycle | |\n| 3.3. . . | 3.3. . . | . . . . . . . . . . . . . . . . | 27 |\n| 3.4. Data-Sharing Models . | 3.4."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Codes for Identification of Federal and Federally-Assisted Organizations:\n\n| 0902 | Botanic Garden |\n|--------|--------------------------------------------------------------------|\n| 0901 | Commission on Security and Cooperation in Europe |\n| 0914 | John C. Stennis Center for Public Service Training and Development |\n| 0904 | Office of Compliance |\n| 0962 | Permanent Committee for the Oliver Wendell Holmes Devise |\n| 0929 | U.S."}], "metadata": {"source": "Codes for Identification of Federal and Federally-Assisted Organizations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST Cloud Computing Forensic Reference Architecture provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-201\n\n## NIST Cloud Computing Forensic Reference Architecture\n\nMartin Herman Michaela Iorga Ahsen Michael Salim Robert H. Jackson Mark R. Hurst Ross A. Leo Anand Kumar Mishra Nancy M. Landreville\n\nYien Wang\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-201\n\n\n\n## NIST Special Publication 800 NIST SP 800-201\n\n## NIST Cloud Computing Forensic Reference Architecture\n\nMartin Herman* Information Access Division Information Technology Laboratory\n\nMichaela Iorga Computer Security Division Information Technology Laboratory\n\nAhsen Michael Salim American Data Technology, Inc. Robert H. Jackson Mark R. Hurst SphereCom Enterprises, Inc. Ross A. Leo University of Houston-Clear Lake The CyberSecurity Institute\n\nAnand Kumar Mishra National Institute of Technology Sikkim India\n\nNancy M. Landreville Graduate School of Cybersecurity and Information Technology University of Maryland (GC)\n\nYien Wang Auburn University\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-201\n\nJuly 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities."}], "metadata": {"source": "NIST Cloud Computing Forensic Reference Architecture", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.8 (NIST 3.3.8)?"}, {"role": "assistant", "content": "According to Guide to Operational Technology (OT) Security:\n\n3.3.8. 3.3.8."}], "metadata": {"source": "Guide to Operational Technology (OT) Security", "cmmc_level": "all", "nist_control": "3.3.8", "cmmc_practice_id": "AU.L2-3.3.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms:\n\nroots of trust in server platforms. The integrity and location data of each host are leveraged in the orchestration and protection of workloads, as well as providing workloads access to specific data.\nWorkload orchestration can ensure that containers are instantiated only on server platforms that meet trustworthiness requirements and are in acceptable locations. Orchestration can also involve initial encryption of container images and releasing the decryption keys only to trusted servers. Additionally, the workloads themselves can be assigned identities based on these trusted attributes of the physical servers they reside on and be granted access to sensitive information based on their identities."}], "metadata": {"source": "Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\nDe-Identifcation . . . . . | 18 |\n| 3.2. | Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .\n| Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 19 |\n| | 3.2.1. | Probability of Re-Identifcation . . . . | 21 |\n| | | 3.2.2. Adverse Impacts of Re-Identifcation . | 24 |\n| | | 3.2.3. Impacts Other Than Re-Identifcation | 26 |\n| | | 3.2.4. Remediation . . . . . . . . . . . . . . . | 27 |\n| | | Data Life Cycle | |\n| 3.3. . . | 3.3. . . | . . . . . . . . . . . . . . . . | 27 |\n| 3.4. Data-Sharing Models . | 3.4."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Understanding Stablecoin Technology and Related Security Considerations:\n\niquidation. This is very similar to the maintenance of margin loans in the stock market. Margin investors in the stock market may be required to post additional collateral to cover stock market loses.\nFor stablecoin systems that utilize data oracles to maintain a parity with their chosen assets, finding the optimal method and frequency for updating the price is critical. If the stablecoin falls out of sync for too long of a period, the system may - in its attempt to correct - overcompensate and cause large price swings. For example, the failure of the IRON stablecoin and its associated $2.2 billion investor loss was that the oracle only updated every 10 minutes, which was insufficient during a period of rapid volatility [36]. Additionally, users may profit by leveraging the latency in the system and knowing how the stablecoin system will react to price updates."}], "metadata": {"source": "Understanding Stablecoin Technology and Related Security Considerations", "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 Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n- [RFC 4492] Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS), May 2006, see https://tools.ietf.org/html/rfc4492. - [RFC 5903] Elliptic Curve Groups Modulo a Prime (ECP Groups) for IKE and IKEv2, June 2010, see https://tools.ietf.org/html/rfc5903. - [RFC 7919] Negotiated Finite Field Diffie-Hellman Ephemeral Parameters, August 2016, see https://tools.ietf.org/html/rfc7919. - [SECG] Standards for Efficient Cryptography Group, see http://www.secg.org/. - [SEC2] Standards for Efficient Cryptography, SEC 2: Recommended Elliptic Curve Domain Parameters, September 2000, see http://www.secg.org/SEC2-Ver1.0.pdf. - [SP 800-38B] Special Publication 800-38B, Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication , May 2005, with updates dated October 2016. https://doi.org/10.6028/NIST.SP.800-38B\n- [SP 800-38C] Special Publication 800-38C, Recommendation for Block Cipher Modes of Operation: the CCM Mode for Authentication and Confidentiality , May 2004, with updates dated July 2007. https://doi.org/10.6028/NIST.SP.800-38C\n- [SP 800-38F] Special Publication 800-38F, Recommendation for Block Cipher Modes of Operation: Methods for Key Wrapping , December 2012. https://doi.org/10.6028/NIST.SP.800-38F\n- [SP 800-52] Special Publication 800-52 Revision 2 (DRAFT), Guidelines for the Selection, Configuration and Use of Transport Layer Security (TLS) Implementations , November 15, 2017. https://csrc.nist.gov/publications/detail/sp/800-52/rev-2/draft\n- [SP 800-56B] Special Publication 800-56B Revision 1, Recommendation for Pair-Wise Key-Establishment Schemes Using Integer Factorization Cryptography , September 2014. https://doi.org/10.6028/NIST.SP.800-56Br1\n- [SP 800-56C] Special Publication 800-56C Revision 1, Recommendation for Key Derivation Methods in Key Establishment Schemes , April 2018."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\nnt of the monitoring strategy is covered in detail in Section 3.6. - Reporting requirements . Reporting requirements do not drive the ISCM strategy but may play a role in the frequency of monitoring.\nFor instance, if OMB policy requires quarterly reports on the number of unauthorized components detected and corrective actions taken, the organization would monitor the system for unauthorized components at least quarterly."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal 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 Risk Assessment?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program:\n\n- SP 800-137A, Assessing Information Security Continuous Monitoring Programs [1]\n- The NIST Cybersecurity Framework (CSF) 2.0 [2]\n- SP 800-30r1 (Revision 1), Guide for Conducting Risk Assessments [3]\n- SP 800-37r2, Risk Management Framework for Information Security Systems and Organizations: A System Life Cycle Approach for Security and Privacy [4]\n- SP 800-161r1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [5]\n- Internal Report (IR) 8286, Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management (ERM) [6]\n\nData from various sources (e.g., vulnerability scans, incident logs, and compliance assessments) can be aggregated to help executives understand information security. Summarizing measurement findings and metrics into concise reports facilitates efficient communication. Regularly reporting on measurement and assessment results fosters transparency, promotes accountability for meeting performance targets, and encourages continuous improvements. Sharing findings with executives demonstrates the organization's commitment to its information security posture.\n\nStakeholder interests may be determined through multiple venues, such as interviews, brainstorming sessions, mission statement reviews, in-house knowledge, and existing findings from risk assessments. There may also be laws and regulations that the organization may need to consider. Input from those who interact with individual systems and existing system-level data will provide targeted insight into the measurement needs of an organization. Ideally, stakeholder interests will be reviewed periodically during the ongoing work of the information security measurement program."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2003 Annual Report:\n\n| Welcome Letter | 2 | |-----------------------------------------------------|-----| | The Computer Security Division Responds to the | | | Federal Information Security Management Act of 2002 | 3 | | Outreach, Awareness and Education | 4 | | Security Management and Guidance | 8 | | Security Testing and Metrics | 14 | | Security Research and Emerging Technologies | 16 | | Cryptographic Standards and Applications | 26 | | Honors and Awards | 32 | | Computer Security Division Publications - 2003 | 34 | | Ways to Engage Our Division & NIST | 36 | - ◆ Standards to be used by Federal agencies to categorize information and information systems based on the objectives of providing appropriate levels of information security according to a range of risk levels - SP 800-37 Guidelines for the Security Certification and Accreditation of Federal Information Technology Systems, second public draft issued June 2003 - ◆ Guidelines recommending the types of information and information systems to be included in each category - FIPS 199 Standards for Security Categorization of Federal Information and Information Systems, public draft issued May 2003 - ◆ Minimum information security requirements (management, operational, and technical security controls) for information"}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Guide to LTE Security:\n\nThe mobile device hardware, mobile operating system (e.g., Android, Blackberry, iOS, Windows Phone), and 3rd party mobile applications are generally out of the scope of this document unless otherwise noted. This document does not analyze non 3rd Generation Partnership Project (3GPP) networks (e.g., WiFi, WiMAX, 3GPP2), forthcoming 3GPP features such as device to device cellular communications and cellular internet of things (IoT), and the over-the-air (OTA) management updates to cellular platforms, and the networks supporting services (e.g Domain Name Services (DNS), Network Time Protocol (NTP)). Supply chain issues relating to cellular networks are also not described. Finally, the IP Multimedia Subsystem (IMS), a modern platform for delivering services such as Voice over LTE (VoLTE), is not included within this document."}], "metadata": {"source": "Guide to LTE Security", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Security-Focused Configuration Management of Information Systems provide? (Part 2)"}, {"role": "assistant", "content": "Circular. 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-128 Natl. Inst. Stand. Technol. Spec. Publ. 800-128, 99 pages (August 2011) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-128\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 for Security-Focused Configuration Management of Information Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Foundational Cybersecurity Activities for IoT Device Manufacturers provide? (Part 5)"}, {"role": "assistant", "content": "The IoT devices in scope for this publication can function on their own, although they may be dependent on specific other devices (e.g., an IoT hub) or systems (e.g., a cloud) for some functionality.\nMany IoT devices have computing functionality, data storage, and network connectivity along with functionality associated with equipment that previously lacked these computing functions (e.g., smart appliances). In turn, these functions enable new efficiencies and technological capabilities for the equipment, such as remote access for monitoring, configuration, and troubleshooting. IoT can also enable the collection and analysis of data about the physical world and use the results to better inform decision making, alter the physical environment, and anticipate future events [1]. IoT devices are acquired and used by many customers: individuals, companies, government agencies, educational institutions, and other organizations. Unfortunately, IoT devices often lack device capabilities that customers can use to help mitigate their cybersecurity risks, such as the functionality customers routinely expect their desktop and laptop computers, smartphones, tablets, and other IT devices to have. Consequently, IoT device customers may have to select, implement, and manage additional or new cybersecurity controls or alter the controls they already have. Compounding this task, customers may not know they need to alter their existing processes to accommodate the unique characteristics of IoT. The result is many IoT devices are not secured in the face of evolving threats; therefore, attackers can more easily compromise IoT devices and use them to harm device customers and conduct additional nefarious acts (e.g., distributed denial of service [DDoS] attacks) against other organizations. 1\n\nThe purpose of this publication is to give manufacturers recommendations for improving how securable the IoT devices they make are."}], "metadata": {"source": "Foundational Cybersecurity Activities for IoT Device Manufacturers", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Trustworthy Email:\n\n| CM-9 | CONFIGURATION MANAGEMENT PLAN | - | CM-9 | CM-9 | |----------------------------------------|--------------------------------------------|----------------------------------------|----------------------------------------|----------------------------------------| | CM-10 | SOFTWARE USAGE RESTRICTIONS | CM-10 | CM-10 | CM-10 | | CM-11 | USER-INSTALLED SOFTWARE | CM-11 | CM-11 | CM-11 | | CONTINGENCY PLANNING | CONTINGENCY PLANNING | CONTINGENCY PLANNING | CONTINGENCY PLANNING | CONTINGENCY PLANNING | | CP-1 | CONTINGENCY PLANNING POLICY AND PROCEDURES | CP-1 | CP-1 | CP-1 | | CP-2 | CONTINGENCY PLAN | CP-2 | CP-2 (1,3,8) | CP-2 (1,2,3,4,5,8) | | CP-3 | CONTINGENCY TRAINING | CP-3 | CP-3 | CP-3 (1) | | CP-4 | CONTIGENCY PLAN TESTING | CP-4 | CP-4(1) | CP-4 (1,2) | | CP-6 | ALTERNATE STORAGE SITE | - | CP-6 (1,3) | CP-6 (1,2,3) | | CP-7 | ALTERNATE PROCESSING SITE | - | CP-7 (1,2,3) | CP-7 (1,2,3,4) | | CP-8 | TELECOMMUNICATION SERVICES | - | CP-8 (1,2) | CP-8 (1,2,3,4) | | CP-9 | SYSTEM BACKUP | CP-9 | CP-9 (1) | CP-9 (1,2,3,5) | | CP-10 | SYSTEM RECOVERY AND RECONSTITUION | CP-10 | CP-10 (2) | CP-10 (2,4) | | CP-11 | ALTERNATE COMMUNICATION PROTOCOLS | - | - | - | | CP-12"}], "metadata": {"source": "Trustworthy Email", "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 AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\n3.1.4 Cryptographic Vulnerability (CWE-310)\n\nDescription\n\nCryptography is the use of mathematical principles and their implementations to ensure that\ninformation is hidden from unauthorized parties, the information is unchanged, and the intended\nparty can verify the sender."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "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 does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines on Security and Privacy in Public Cloud Computing:\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 discusses ITL's research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations.\n\nMaintaining physical and logical security over clients can be troublesome, especially with embedded mobile devices such as smart phones. Their size and portability can result in the loss of physical control. Built-in security mechanisms often go unused or can be overcome or circumvented without difficulty by a knowledgeable party to gain control over the device. Moreover, cloud applications are often delivered to them through custom-built native applications (i.e., apps) rather than a Web browser.\n\nThe two lowest layers shown denote the physical elements of a cloud environment, which are under the full control of the cloud provider, regardless of the service model. Heating, ventilation, air conditioning (HVAC), power, communications, and other aspects of the physical plant form the bottom layer, the facility layer , while computers, network and storage components, and other physical computing infrastructure elements form the hardware layer immediately above it."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "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 Cybersecurity Framework Profile for Liquefied Natural Gas:\n\n| Priority Cybersecurity Framework Subcategories by Mission Objective ................... | Priority Cybersecurity Framework Subcategories by Mission Objective ................... | 23 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| References...................................................................................................................................47 | References...................................................................................................................................47 | References...................................................................................................................................47 |\n| Appendix A."}], "metadata": {"source": "Cybersecurity Framework Profile for Liquefied Natural Gas", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Representation of PIV Chain-of-Trust for Import and Export:\n\nmay be maintained in a chain-of-trust record. As per FIPS 201-2, 'a card issuer may optionally maintain, for each PIV Card issued, a documentary chain-of-trust for the identification data it collects.\nThe chain-of-trust is a sequence of related enrollment data records that are created and maintained through the methods of contemporaneous acquisition of data within each enrollment data record, and biometric matching of samples between enrollment data records.'"}], "metadata": {"source": "Representation of PIV Chain-of-Trust for Import and Export", "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 Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992 provide? (Part 4)"}, {"role": "assistant", "content": "y^:-0fm- X;d' - Sx.p<sttt^p: - , 7 .•-.: :i^mm'm$< O^^Xd^-r X-;' ,-'^7:i ' ••' ' , ;, ' '' 1 ; ## Contents | 1 Executive Summary | 1 Executive Summary | 1 Executive Summary | 1 | |----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------| | | | | 1 | | 1.1 Purpose of the Workshop | 1.1 Purpose of the Workshop | 1.1 Purpose of the Workshop | | | 1.2 Structure of the Workshop 1.3 Workshop Recommendations | 1.2 Structure of the Workshop 1.3 Workshop Recommendations | 1.2 Structure of the Workshop 1.3 Workshop Recommendations | 1 | | 2 Workshop Participants | 2 Workshop Participants | 2 Workshop Participants | 4 | | 3 Introductory Session | 3 Introductory Session | 3 Introductory Session | 5 | | 4 | Session on Authentication in Distributed Networks | Session on Authentication in Distributed Networks | 7 | | | | Standards and Technology | 7 | | 4.2 General Discussion on Authentication 5 Session on Access Control in Distributed Networks | 4.2 General Discussion on Authentication 5 Session on Access Control in Distributed Networks | 4.2 General Discussion on Authentication 5 Session on Access Control in Distributed Networks | | | | |"}], "metadata": {"source": "Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to CMVP Approved Non-Invasive Attack Mitigation Test Metrics_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "CMVP Approved Non-Invasive Attack Mitigation Test Metrics_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to ISCMA_ An Information Security Continuous Monitoring Program Assessment:\n\nThe Restart Assessment action allows modification of the three assessment parameters-risk management level, depth, and breadth-that are described in Section 3.5."}], "metadata": {"source": "ISCMA_ An Information Security Continuous Monitoring Program Assessment", "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 Recommended Cybersecurity Requirements for Consumer-Grade Router 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. 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 leade rship 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 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. | 1. Introduction.....................................................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Scope of Consumer-Grade Routers...................................................................................................5 |\n| 3."}], "metadata": {"source": "Recommended Cybersecurity Requirements for Consumer-Grade Router Products", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Guidelines for Securing Radio Frequency Identification (RFID) Systems:\n\n3.1.4 | Matching... 3.1.4 Functionality\n\nThe primary function of a tag is to provide an identifier to a reader, but many types of tags support additional capabilities that are valuable for certain business processes. 3.1.4 Matching\n\nIn a matching application , two tagged items are matched with each other and a signal (e."}], "metadata": {"source": "Guidelines for Securing Radio Frequency Identification (RFID) Systems", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.3 (NIST 3.4.3)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile:\n\n3.4.3. 3.4.3. 3.4.3."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile", "cmmc_level": "all", "nist_control": "3.4.3", "cmmc_practice_id": "CM.L2-3.4.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Small Business Information Security_ The Fundamentals:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems.\n\nThe authors, Celia Paulsen and Patricia Toth wish to thank Richard Kissel and Dr. Hyunjeong Moon for their extensive contributions to this publication. Since 2002, NIST along with the Small Business Administration and the Federal Bureau of Investigation's InfraGard program, has conducted research and outreach to small businesses - much of this publication is thanks to their generous time and effort. The authors would like to thank their partners and the small businesses who contributed to this work. In addition, they would like to thank those colleagues and reviewers who contributed to the document's development."}], "metadata": {"source": "Small Business Information Security_ The Fundamentals", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Science Challenges:\n\nDynamic Host Configuration Protocol | FC ID | Short Title | Challenge | Description | Result of Overcoming Challenge | |---------|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | FC-15 | Malicious code may circumvent VMisolation methods | Malicious code may circumvent virtual machine isolation methods and interfere with the hypervisor or other guest virtual machines | Vulnerabilities in server virtualization allow an attacker to escape from a guest virtual machine to another guest or to the hypervisor itself."}], "metadata": {"source": "NIST Cloud Computing Forensic Science 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 additional guidance does Computer Security Division 2005 Annual Report provide? (Part 5)"}, {"role": "assistant", "content": "ments and results of security program assessments - SP 800-26 Revision 1, Guide for Information Security Program Assessments and System Reporting Form (first public draft issued August 2005).\n- Bring the security planning process up to date with key standards and guidelines developed by NIST - SP 800-18 Revision 1, Guide for Developing Security Plans for Federal Information Systems (first public draft issued August 2005). - Provide assistance to Agencies and private sector - Conduct ongoing, substantial reimbursable and non-reimbursable assistance support, including many outreach efforts such as the Federal Information Systems Security Educators' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSM Forum), the Small Business Corner, and the Program Review for Information Security Management Assistance (PRISMA). - Evaluate security policies and technologies from the private sector and national security systems for potential Federal agency use - Host a growing repository of Federal agency security practices, public/private security practices, and security configuration checklists for IT products. In conjunction with the Government of Canada's Communications Security Establishment, CSD leads the Cryptographic Module Validation Program (CMVP). The Common Criteria Evaluation and Validation Scheme (CCEVS) and CMVP facilitate security testing of IT products usable by the Federal government. - Solicit recommendations of the Information Security and Privacy Advisory Board on draft standards and guidelines - Solicit recommendations of the Board regularly at quarterly meetings. - Provide outreach, workshops, and briefings - Conduct ongoing awareness briefings and outreach to our customer community and beyond to ensure comprehension of guidance and awareness of planned and future activities."}], "metadata": {"source": "Computer Security Division 2005 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 PIV Data Model Test Guidelines:\n\n| Precondition(s) | 1. A valid PIV card is inserted into the contact reader. h card handle. on the PIV card. 2. A valid PC/SC connection exists between the test application and the contact reader. 3. The test application is currently connected to the card application which is accessible throug 4. A valid CCC is present |\n|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Test Scenario | 1. Set cardHandle := <>. .0)>>. 2. Set OID := <\n\n## NISTIR 8374\n\n## Ransomware Risk Management:\n\nA Cybersecurity Framework Profile\n\nWilliam C. Barker Dakota Consulting Silver Spring, MD\n\nWilliam Fisher\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nMurugiah Souppaya\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8374\n\nFebruary 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\n## National Institute of Standards and Technology Interagency or Internal Report 8374 28 pages (February 2022)\n\n## This publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8374\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": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\nEXECUTIVE SUMMARY .................................................................................................................. IX\nContent of the Report ............................................................................................................................ xi\n CHAPTER 1 DOCUMENT DEVELOPMENT STRATEGY ...................................................................1\n1.1 Cybersecurity and the Electric Sector ............................................................................................ 4\n1.2 Scope and Definitions .................................................................................................................... 5\n1.3 Smart Grid Cybersecurity Document Development Strategy ........................................................ 6\n1.4 Combined Cyber-Physical Attacks .............................................................................................. 12\n CHAPTER 2 LOGICAL ARCHITECTURE AND INTERFACES OF THE SMART GRID ......................14\n2.1 The Seven Domains to the Logical Reference Model ................................................................. 15\n2.2 Logical Security Architecture Overview ..................................................................................... 24\n2.3 Logical Interface Categories ........................................................................................................ 28\n CHAPTER 3 HIGH-LEVEL SECURITY REQUIREMENTS ...............................................................75\n3.1 Cybersecurity Objectives ............................................................................................................. 75\n3.2 Confidentiality, Integrity, and Availability Impact Levels .......................................................... 76\nImpact Levels for the CI&A Categories ......................................................................................"}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to Fiscal Year 2023 Cybersecurity and Privacy Annual Report:\n\n\n\n\n\n## 2023 Cybersecurity & Privacy Annual Report\n\n## Fiscal Year 2023 Cybersecurity and Privacy Annual Report\n\nPatrick O'Reilly, Editor Computer Security Division Information Technology Laboratory\n\nKristina Rigopoulos, Editor Applied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-229\n\nMay 2024\n\n\n\nU.S. DEPARTMENT OF COMMERCE Gina M. Raimondo, Secretary\n\n\n\n\n\n- Cryptography 5\n\nIntroduction\n\n4\n\n- Education, Training & Workforce Development 7\n- Emerging Technologies 9\n- HumanCentered Cybersecurity 11\n- Identity & Access Management 13\n- Privacy 15\n- Risk Management 17\n- Trustworthy Networks & Platforms 19\n- NIST National\n- Cybersecurity Center of Excellence 21\n\n\n\n\n\n--------------------------\n\nThis year has been one to remember! As we wrapped up our celebration of 50 years of work in cybersecurity, we continued to prioritize our quest for deep collaboration with the community and seamless coordination across NIST throughout 2023. Our research and demonstrated practical applications work spanned across several key priority areas, which are outlined in this report-with hyperlinked pointers to more specifics if you'd like to dig deeper or learn more. NIST's work meshes well with - and is a key part of - the National Cybersecurity Strategy and the related Implementation Plan. NIST is singled out for its work related to international standards, an area that we have prioritized and is yielding notable results. In the same vein, the U.S."}], "metadata": {"source": "Fiscal Year 2023 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N 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-178 Natl. Inst. Stand. Technol. Spec. Publ. 800-178, 68 pages ( Octo ber 2016) CODEN: NSPUE2\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-178\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": "A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Personnel Security?"}, {"role": "assistant", "content": "According to Security Segmentation in a Small Manufacturing Environment:\n\n| Common Weakness | Security Segmentation |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Incomplete or nonexistent asset inventory: without an asset inventory, it is difficult to identify vulnerabilities or to mitigate them in devices and on the network. | Security segmentation identifies assets and groups them into security zones, which can help with inventory management. Asset inventory is an intrinsic part of security segmentation."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Measuring the Usability and Security of Permuted Passwords on Mobile Platforms provide? (Part 3)"}, {"role": "assistant", "content": "## Abstract\n\nPassword entry on mobile devices significantly impacts both usability and security, but there is a lack of usable security research in this area, specifically for complex password entry.\nTo address this research gap, we set out to assign strength metrics to passwords for which we already had usability data, in an effort to have a more meaningful comparison between usability and security. This document reports a method of optimizing the input of randomly generated passwords on mobile devices via password permutation to allow for a comparison of password usability data. We found that the number of keystrokes saved-the efficiency gained-via permutation depends on the number of onscreen keyboard changes required in the original password rather than on password length. Additionally, we created and are releasing Python scripts (publicly available from https://github.com/usnistgov/PasswordMetrics) for the experiments on entropy loss we conducted across passwords ranging in length from 5 to 20 characters. ## Keywords\n\nauthentication; mobile devices; onscreen keyboards; password entry; password generation; password permutation; security-usability balance; text entry; usable security\n\n## Acknowledgments\n\nThe authors wish to thank their colleagues who reviewed drafts of this report and contributed to its technical content, including Sharon Laskowski, Kerry McKay, Ray Perlner, Andrew Regenscheid, Mary Theofanos, and Meltem Sönmez Turan of NIST. Thank you to Kenneth Thompson and others for assistance with obtaining screenshots of mobile platforms. A very special thanks to Jim Filliben and Andrew Rukhin for their mathematical consultation, and especially to Andrew for his formulas presented in Appendix D. ## Audience\n\nThis document is intended for those researchers in the usable security field, regardless of whether their background is primarily usability or primarily security."}], "metadata": {"source": "Measuring the Usability and Security of Permuted Passwords on Mobile Platforms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- The primary function of the first generation of CASBs was the discovery of resources. They provided visibility into all of the cloud resources that the enterprise users accessed, thus preventing or minimizing the chances of shadow IT. Shadow IT is the practice of some users using cloud applications that are not authorized by the enterprise IT management from home or the office using enterprise desktops. An example of this is the use of unapproved software as-a-service (SaaS) applications for file sharing, social media, collaboration, and web conferencing [4]. This generation of CASBs also provides some statistics, such as software-as-a-service (SaaS) utilization. - The current generation of CASBs enforces security and governance policies for cloud applications, thus enabling enterprises to extend their on-premises policies to the cloud. Specific security services provided by CASBs include:\n- o Protection of enterprise data that live in cloud service providers' servers (due to SaaS or IaaS subscriptions), as well as data inflow and data outflow (i.e., Data Loss Prevention [DLP] capabilities) from those servers. - o Tracking of threats, such as account hijacking and other malicious activities, some of which can detect anomalies in users' cloud access behavior (through robust User and Entity Behavior Analytics (UEBA) functionality) and stop insider threats and advanced cyberattacks [5]. - o Detection of misconfigurations in the enterprise's subscribed IaaS and cloud servers. These misconfigurations pose serious security risks, such as data breaches. Alerts generated by CASB due to misconfigurations in the enterprise's IaaS deployments direct the enterprise to follow guidelines, such as the Center for Internet Security's (CIS) benchmarks for public cloud services, thus improving the overall security profile of the enterprise for cloud access [4]."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Codes for Identification of Federal and Federally-Assisted Organizations:\n\nThis document provides the organizational codes for federal agencies to establish the Federal Agency Smart Credential Number (FASC-N) that is required to be included in the FIPS 201 Card Holder Unique Identifier. SP 800-87 is a companion document to FIPS 201.\n\nCHUID; Federal Agency Smart Credential Number (FASC-N); FIPS 201; HSPD-12; organizational codes; identity credential; PIV cards.\n\nThe Homeland Security Presidential Directive HSPD-12 called for new standards to be adopted governing the interoperable use of identity credentials to allow physical and logical access to Federal government locations and systems. Personal Identity Verification (PIV) for Federal Employees and Contractors , (Federal Information Processing Standard 201 (FIPS 201)) was developed to establish standards for identity credentials. This document, Special Publication (SP) 800-87, provides the organizational codes necessary to establish the PIV Federal Agency Smart Credential Number (PIV FASC-N) that is required to be included in the FIPS 201 Card Holder Unique Identifier (CHUID) and is a companion document to FIPS 201."}], "metadata": {"source": "Codes for Identification of Federal and Federally-Assisted Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to An Introduction to Information Security:\n\n| | 6.3 Implement ....................................................................................................... 37 |\n|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|\n| 6.4 Assess ............................................................................................................ | 37 |\n| 6.5 Authorize......................................................................................................... | 37 |\n| 6.6 Monitor............................................................................................................ | 37 |\n| 7 Assurance.............................................................................................................38 | |\n| 7.1 Authorization ..................................................................................................."}], "metadata": {"source": "An Introduction to Information 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to BIOS Protection Guidelines:\n\n| Introduction.......................................................................................................................1-1 | | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Authority ...................................................................................................................1-1 | | | 1.2 | Purpose and Scope..................................................................................................1-1 | | | 1.3 | Audience ..................................................................................................................1-2 | | | 1.4 | Document Structure .................................................................................................1-2 | | 2."}], "metadata": {"source": "BIOS Protection Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\nAnalysis | | RS | Respond | RS.MI | Mitigation | | RS | Respond | RS.IM | Improvements | | RC | Recover | RC.RP | Recovery Planning | | RC | Recover | RC.IM | Improvements | | RC | Recover | RC.CO | Communications |"}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to Operational Technology (OT) Security:\n\nsecurity control baselines for low-, moderate-, and high-impact OT systems\n\n2.3.4. Programmable Logic Controller-Based Topologies ..................................................21\n\n3.3.4. Define OT-Specific Policies and Procedures ...........................................................40"}], "metadata": {"source": "Guide to Operational Technology (OT) Security", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities:\n\nA security configuration setting is an element of a software's security that can be altered through the software itself. Examples of settings are an operating system offering access control lists that set the privileges that users have for files, and an application offering a setting to enable or disable the encryption of sensitive data stored by the application. A security configuration issue vulnerability involves the use of security configuration settings that negatively affect the security of the software.\n\nCCE-3245-8 in Windows XP is: 'IPSEC Services.' This service can be enabled or disabled. This service can protect the confidentiality and integrity of network traffic, and some IPsec services (such as on Windows systems) also perform packet filtering (firewall capabilities). So if the service is disabled but should be enabled, it could expose the system's network services to unauthorized access from other systems (partial impact on confidentiality) and also permit network traffic to be transmitted without expected confidentiality or integrity protections (partial impact on confidentiality and integrity). Some network communications may require IPsec protection, so in those cases the traffic could not be sent (partial impact on availability). The Privilege Level would be 'Not Defined.'\n\nwith the system (e.g., if IPsec is required for communications but unavailable). The Exploitation Method is 'Passive' and Access Complexity is 'Low' because no specific actions need to be performed, and Authentication is 'None'."}], "metadata": {"source": "The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Technical Guide to Information Security Testing and Assessment:\n\n| 6.4 | Assessment Logistics ..............................................................................................6-4 | Assessment Logistics ..............................................................................................6-4 | | |-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------| | | 6.4.1 | Assessor Selection and Skills.......................................................................6-5 | | | | 6.4.2 | Location Selection ........................................................................................6-6 | | | | 6.4.3 | Technical Tools and Resources Selection | ...................................................6-8 | | 6.5 | Assessment Plan Development.............................................................................6-10 | Assessment Plan Development.............................................................................6-10 | | | 6.6 | Legal Considerations .............................................................................................6-12 | Legal Considerations .............................................................................................6-12 | | | 6.7 | Summary................................................................................................................6-12 | Summary................................................................................................................6-12 | | | 7."}], "metadata": {"source": "Technical Guide to Information Security Testing and Assessment", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guidelines on Security and Privacy in Public Cloud Computing:\n\nPublic cloud computing represents a significant paradigm shift from the conventional norms of an organizational data center to a deperimeterized infrastructure open to use by potential adversaries. As with any emerging information technology area, cloud computing should be approached carefully with due consideration to the sensitivity of data. Planning helps to ensure that the computing environment is as secure as possible and in compliance with all relevant organizational policies and that privacy is maintained. It also helps to ensure that the agency derives full benefit from information technology spending. To maximize effectiveness and minimize costs, security and privacy must be considered throughout the system lifecycle from the initial planning stage forward. Attempting to address security and privacy issues after implementation and deployment is not only much more difficult and expensive, but also exposes the organization to unnecessary risk."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "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 Access Control?"}, {"role": "assistant", "content": "According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0:\n\n........................................................ | 1. INTRODUCTION..............................................................................................................................\n| 1 |\n| 1.1 | I DENTIFICATION...........................................................................................................................1 | |\n| 1.2 | OVERVIEW....................................................................................................................................1 | |\n| 2. TOE DESCRIPTION......................................................................................................................... | 2. TOE DESCRIPTION........................................................................................................................."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT):\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-  Connected vehicle IoT enables vehicles, roads, and other infrastructure to communicate and share vital transportation information.\n-  Consumer IoT consists of IoT applications in residences as well as wearable and mobile devices.\n-  Health IoT processes data derived from sources such as electronic health records and patient-generated health data.\n-  Smart building IoT includes energy usage monitoring systems, physical access control security systems and lighting control systems.\n-  Smart manufacturing IoT enables enterprise-wide integration of data, technology, advanced manufacturing capabilities, and cloud and other services.\n\napplication areas makes it clear that cybersecurity for IoT is unique and requires tailoring existing standards and creating new standards to address challenges, for example: pop-up network connections, shared system components, the ability to change physical aspects of the environment, and related connections to safety."}], "metadata": {"source": "Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.3. 3.2.3 requires a physical authenticator to be\nauthenticated along with a biometric comparison. 3.2.3 requires a physical authenticator to be\nauthenticated along with the biometric comparison."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI:\n\nProduct: Solaris 2.3 CRAY Version R Maintenance Update 1 with Patch\n\nUpdates\n\nUpdates"}], "metadata": {"source": "Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI", "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 Computer Security Division 2003 Annual Report:\n\n## CONFIGURATION MANAGEMENT AND CONTROL\n\nFederal agencies will be required to use FIPS Publication 199 standards to define security categories for their information systems. The recommendations for baseline (minimum) security controls from Special Publication 80053 can subsequently be used as a starting point for and input to the organization's risk assessment processes and the development of security plans for those information systems. While the FIPS Publication 199 security categorization associates the operation of the information system with a 'worst-case' impact on an organization's operations and assets (providing an upper bound on risk), the incorporation of refined threat and vulnerability information during the risk assessment process facilitates the tailoring of the baseline security controls to address organizational needs and tolerance for risk. Deviations from the recommended baseline security controls should be documented (along with supporting rationale) in the security plan for the information system. The use of security controls from Special Publication 800-53 and the incorporation of baseline (minimum) controls as a starting point in the control selection process facilitate a more consistent level of security in an organizational information system. At the same time it offers the needed flexibility to fine tune and adjust the controls based on specific organizational policy and requirements documents, particular conditions and circumstances, known threat and vulnerability information, or tolerance for risk to the organization's operations and assets. One of the newer features added to the FASP Web site are IT product specific checklists for settings and configurations. These checklists are discussed more fully earlier in this report. These checklists are recommendations, not mandatory requirements, and are offered freely to IT professionals."}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\n| Table 6-2. | Summary of Security Claims for Selected EAP Methods ......................................6-11 | |\n|--------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------|\n| Table 6-3. | Characteristics of Common TLS-Based EAP Methods for WLANs.......................6-12 | |\n| Table 6-4. | Questions for Identifying an Appropriate EAP Method | ..........................................6-13 |\n| Table 6-5. | EAP Multiplexing Model.........................................................................................6-16 | |\n| Table 6-6. | EAP Support Requirements for WLAN Components.............................................6-18 | |\n| Table 7-1. | Wi-Fi Alliance Certification Programs ......................................................................7-2 | |\n| Table 7-2. | IEEE 802.11i Features Not Present in WPA............................................................7-3 | |\n| Table 8-1. | IEEE 802.11 RSN Security Checklist: Initiation Phase............................................8-3 | |\n| Table 8-2. | IEEE 802.11 RSN Security Checklist: Planning and Design Phase........................8-7 | |\n| Table 8-3."}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "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 Access Control?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\n| 1.4 | Terminology | 1-7 |\n| | 1.5 | Document Organization | 1-7 |\n| 2.\n| Rationale | Rationale | 2-1 |\n| | 2.1 | Intended Method of Use | 2-1 |\n| | 2.2 | Environmental Assumptions | 2-1 |\n| | 2.3 | Expected Threats | 2-2 |\n| | 2.4 | Security Features and Assurances | 2-2 |\n| | | 2.4.1 Identification and Authentication | 2-3 |\n| | 2.4.2 | Access Control | 2-3 |\n| | 2.4.3 | Audit | 2-3 |\n| | 2.4.4 | System Integrity | 2-4 |\n| | 2.4.5 | Data Integrity | 2-4 |\n| | 2.4.6 | Reliability of Service | 2-4 |\n| | 2.4.7 | Product Development Assurance | 2-4 |\n| | 2.4.8 | Product Documentation Assurance | 2-5 |"}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.3.2. 3.3.2. 3.3.2."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management:\n\n3.2.2) will help determine those dependencies. 3.2.2 Three-Point Estimation\n\nOne method for considering the likelihood or impact of a risk event is three-point estimation."}], "metadata": {"source": "Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Framework for Designing Cryptographic Key Management Systems provide? (Part 5)"}, {"role": "assistant", "content": "....................................................................................... | 1. Introduction ..............................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 Scope of this | 1.1 Scope of this | Framework........................................................................................ 3 |\n| 1.2 Audience................................................................................................................. | 1.2 Audience................................................................................................................."}], "metadata": {"source": "A Framework for Designing Cryptographic Key Management Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\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\npublication, including concepts and methodologies, may be used by Federal agencies even before\nthe completion 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. 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 tests, test\nmethods, reference data, proof of concept implementations, and technical analyses to advance\nthe development and productive use of information technology. ITL’s responsibilities include the\ndevelopment of management, administrative, technical, and physical standards and guidelines\nfor the cost-effective security and privacy of other than national security-related information in\nFederal information systems. EXECUTIVE SUMMARY .................................................................................................................. IX\nContent of the Report ............................................................................................................................ xi\n CHAPTER 1 DOCUMENT DEVELOPMENT STRATEGY ...................................................................1\n1.1 Cybersecurity and the Electric Sector ............................................................................................ 4\n1.2 Scope and Definitions ...................................................................................................................."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\n- Sensitivity (e.g., sensitive vs. non-sensitive)\n- Frequency (e.g., frequently accessed vs. non-frequently accessed)\n- Environment (e.g., Production vs. Development vs. Testing vs. Staging)\n\nPoint-in-time copies, are usually created by the immediate element storing the source data (e.g., storage array, filesystem, database), and are designated for fast recovery and a wide variety of other uses, such as cloning production data for testing purposes. Point-in-time copies can also be taken from remote replicas (and thus can be referred to as 'remote Point-in-time copies').\n\nUnpatched vulnerabilities are unintended software side effects or dependencies not caught by software quality assurance (QA) or testing that, if exploited, present a security risk."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\n## AS06.01.05: The eContentType of the encapContentInfo shall be id-PIVCHUIDSecurityObject (OID = 2.16.840.1.101.3.6.1).\n\n## AS06.01.13: The signedAttrs of the SignerInfo shall include the pivSigner-DN (OID = subject name that appears in the X.509 certificate for the entity that signed the CHUID. 2.16.840.1.101.3.6.5) attribute containing the\n\n## .101.3.6.7). AS06.01.16: The digital signature certificate used to sign the CHUID shall in the extKeyUsage assert id-PIV-content-signing (OID = 2.16.840.1"}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks:\n\n- IoT sensor data, representing measurements of the physical world, always has uncertainties associated with it. Effective management of IoT sensor data, including understanding uncertainties, is necessary to assess data quality and meaning so the organization can make decisions regarding the data's use and avoid introducing new risks. Without this, error rates may be unknown for the different contexts in which an IoT device might be used. 1 Effective IoT sensor data management is important when mitigating physical attacks on sensor technology, such as attacks performed through wireless signals, that could cause sensors to produce false results. - The ubiquity of IoT sensors in public and private environments can contribute to the aggregation and analysis of enormous amounts of data about individuals. These activities can be used to influence individuals' behavior or decision-making in ways they do not understand, or lead to information being revealed that individuals did not want revealed, including the re-identification of previously de-identified PII-and may be beyond the originally intended scope of the IoT device's operation. - IoT devices with actuators have the ability to make changes to physical systems and thus affect the physical world. The potential impact of this needs to be explicitly recognized and addressed from cybersecurity and privacy perspectives. In a worst-case scenario, a compromise could allow an attacker to use an IoT device to endanger human safety, damage or destroy equipment and facilities, or cause major operational disruptions. Privacy concerns and related civil liberties concerns could arise through authorized changes to physical systems that could impact individuals' physical autonomy or behavior in personal and public spaces."}], "metadata": {"source": "Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\nOrganizations should provide adequate staffing with the appropriate training such that support is available in a timely manner (consistent with thresholds defined in the organization's business plan). Stakeholders are advised to use other Functions within the Cybersecurity Framework to inform the identification and prioritization procedures. For example, while testing business continuity procedures, use the findings to identify which resources of the mission were impacted and to what degree, and | [NIST-SP800-37r2] [NIST-SP800-53r5] AC-20, CP-2, CP-8, RA-2, RA-9, SA-20, SC-6 |\n| ID.AM-6 : Cybersecurity roles and responsibilities for the entire workforce and third- party stakeholders (e.g., suppliers, customers, partners) are established | Organizations should assign cybersecurity roles and responsibilities for the ground systems. The roles and responsibilities for third-party stakeholders and collaborative partners (such as organizations that own or operate payloads that are hosted) are determined on a case-by-case basis. | [NIST-SP800-53r5] CP-2, PM-2, PM-29,PS-2, PS-7 |\n| Identify: Business Environment Category The organization's mission, objectives, stakeholders, and activities are documented, reviewed, and prioritized. This information is used to inform cybersecurity roles, responsibilities, and risk management decisions. | Identify: Business Environment Category The organization's mission, objectives, stakeholders, and activities are documented, reviewed, and prioritized."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\nTraceability of SWAMControl Items to Example Attack Steps................... A-1 |\n| Appendix B. Keyword Rules Used to Identify Controls that Support SWAM....................B-1 |\n| False Positives................................................................................................................ C-1 Appendix D. Control Items Not in the Low, Moderate, or High Baselines......................... D-1 |\n| Appendix E. SWAM-Specific Acronyms and Abbreviations* ..............................................E-1 |\n| Appendix F. Glossary ................................................................................................................F-1 |\n| Appendix G. Control Items Affecting Desired and/or Actual State from All Defect Checks in this Volume................................................................................................................G-1 |"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms provide? (Part 3)"}, {"role": "assistant", "content": "today's cloud data centers and edge computing, attack surfaces have significantly increased, cyber attacks are industrialized, and most security control implementations are not coherent or consistent.\nThe foundation of any data center or edge computing security strategy should be securing the platform on which data and workloads will be executed and accessed. The physical platform represents the foundation for any layered security approach and provides the initial protections to help ensure that higher-layer security controls can be trusted. This report explains an approach based on hardware-enabled security techniques and technologies for safeguarding container deployments in multi-tenant cloud environments. It also describes a prototype implementation of the approach intended to be a blueprint or template for the general security community. ## Keywords\n\ncloud; container; hardware-enabled security; hardware root of trust; platform security; trusted compute pool; virtualization. ## Audience\n\nThe primary audiences for this report are security professionals, such as security engineers and architects; system administrators and other information technology (IT) professionals for cloud service providers; and hardware, firmware, and software developers who may be able to leverage hardware-enabled security techniques and technologies to improve container deployment in multi-tenant cloud environments. ## Trademark Information\n\nAll registered trademarks or other trademarks belong to their respective organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cloud Computing Synopsis and Recommendations:\n\n| Executive Summary.................................................................................................................\n1 |\n|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1. | Introduction.................................................................................................................... | Introduction...................................................................................................................."}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThe National Institute of Standards and Technology (NIST) hosted an in-person, all-day workshop on February 27, 2024, to discuss existing and emerging cybersecurity threats and mitigation techniques for semiconductors throughout their life cycle. The workshop obtained valuable feedback from industry, academia, and government to inform NIST's development of cybersecurity and supply chain standards, guidance, and recommended practices. The discussion focused on semiconductor development and highlighted cybersecurity measurements and metrics that utilize reference data sets to facilitate the testing, attestation, certification, verification, and validation of semiconductor components. It also emphasized the use of automated cybersecurity tools and techniques to secure manufacturing environments throughout the development life cycle. This report summarizes the content that was presented and discussed at the workshop. These activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle. The last panel member was Matthew Areno, Senior Principal Engineer for Intel Corporation. Matthew admitted that there is no industry standard to describe the phases of the supply chain for ICs."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products:\n\n- Multiple signatures for software update packages when possible. At a minimum, all software update packages should be signed by the source of the update (e.g., manufacturer). When applicable (e.g., when routers are leased from internet service providers (ISPs) other entities, such as the owning ISP, may also cryptographically sign updates, adding another layer of security. Routers would only apply a software update if the cryptographic signatures from both the manufacturer and ISP are verified. Cosigning by the ISP also gives the ISP a mechanism to manage the acceptance of software updates. - Robust security for protecting logs of captured cybersecurity state information. Cybersecurity State Awareness, documented in Appendix A, is essential for detecting compromised routers. Because logs can be a valuable tool for security researchers and others performing forensic analysis of cybersecurity incidents, this data needs to be stored securely. Protections that can enhance router log security include encrypting and password protecting logs to ensure that access is limited to authorized personnel only, use of non-volatile memory storage for logs, off-device storage for logged data, and restricting log deletion. | SSDF Task | Recommended for Router… |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|\n| PO.1.1: Identify and document all security requirements for the organization's software development infrastructures and processes and maintain the requirements over time. | Firmware, Mobile App., Web App."}], "metadata": {"source": "Recommended Cybersecurity Requirements for Consumer-Grade Router Products", "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 The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide? (Part 5)"}, {"role": "assistant", "content": "edge and skills for security awareness professionals within the federal government. The following is a high-level overview of these results, with statistics from the survey unless otherwise indicated.\n## Security Awareness Duties and Work Roles\n\n- 90% of survey participants performed security awareness duties on a part-time basis, with just over 55% spending 25% or less of their time. Focus group participants had similar allocations: 93% part-time and 39% spending 25% of less time. - 50% of survey participants either did not know or were not sure of their National Initiative for Cybersecurity Education (NICE) Workforce Framework for Cybersecurity (NICE Framework) Work Role. This was despite the Federal Cybersecurity Workforce Assessment Act which requires federal agencies to assign the NICE Framework coding structure to its cybersecurity and information technology (IT) positions. Those participants who knew their Work Role identified 11 unique Work Roles. ## Professional Backgrounds\n\n- Participants were diverse in their educational backgrounds, with 83% from focus group and 51% from the survey indicating that they have at least one non-STEM degree. - 92% of survey participants had worked in cybersecurity positions and 76% had worked in IT jobs that did not have a cybersecurity focus. Less than 25% had worked in a variety of\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\nother fields, including non-IT fields such as instructional design and education, communications, and human resources. We found that 40% of participants had only ever worked in a technical field (cybersecurity, IT, or software development). ## Knowledge and Skills\n\n- Survey participants rated the importance of having specific knowledge and skills represented on their teams."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Security Guidance for First Responder Mobile and Wearable Devices:\n\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|\n| | 1.1 Purpose | .......................................................................................................... 1 |\n| | 1.2 Scope.............................................................................................................. | 2 |\n| | 1.3 Document Structure........................................................................................"}], "metadata": {"source": "Security Guidance for First Responder Mobile and Wearable 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 does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security Considerations for Voice Over IP Systems:\n\n- Separate voice and data on logically different networks if feasible. Different subnets with separate RFC 1918 address blocks should be used for voice and data traffic, with separate DHCP servers for each, to ease the incorporation of intrusion detection and VOIP firewall protection\n- At the voice gateway, which interfaces with the PSTN, disallow H.323, SIP, or other VOIP protocols from the data network. Use strong authentication and access control on the voice gateway system, as with any other critical network component. Strong authentication of clients towards a gateway often presents\n\n- difficulties, particularly in key management. Here, access control mechanisms and policy enforcement may help. - ƒ A mechanism to allow VOIP traffic through firewalls is required. There are a variety of protocol dependent and independent solutions, including application level gateways (ALGs) for VOIP protocols, Session Border Controllers, or other standards-based solutions when they mature. - ƒ Stateful packet filters can track the state of connections, denying packets that are not part of a properly originated call. (This may not be practical when multimedia protocol inherent security or lower layer security is applied, e.g., H.235 Annex D for integrity provision or TLS to protect SIP signaling.)\n- ƒ Use IPsec or Secure Shell (SSH) for all remote management and auditing access. If practical, avoid using remote management at all and do IP PBX access from a physically secure system. - If performance is a problem, use encryption at the router or other gateway, not the individual endpoints, to provide for IPsec tunneling. Since some VOIP endpoints are not computationally powerful enough to perform encryption, placing this burden at a central point ensures all VOIP traffic emanating from the enterprise network has been encrypted. Newer IP phones are able to provide Advanced Encryption System (AES) encryption at reasonable cost."}], "metadata": {"source": "Security Considerations for Voice Over IP Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide for Conducting Risk Assessments:\n\n3 While federal agencies are required to follow certain specific NIST Special Publications in accordance with OMB policy, there is flexibility in how agencies apply the guidance. Federal agencies apply the security concepts and principles articulated in the NIST Special Publications in accordance with and in the context of the agency's missions, business functions, and environment of operation. Consequently, the application of NIST guidance by federal 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. Given the high priority of information sharing and transparency within the federal government, agencies also consider reciprocity in developing their information security solutions. When assessing federal agency compliance with NIST Special Publications, Inspectors General, evaluators, auditors, and assessors consider the intent of the security concepts and principles articulated within the specific guidance document and how the agency applied the guidance in the context of its mission/business responsibilities, operational environment, and unique organizational conditions. - Individuals with information security/risk assessment and monitoring responsibilities (e.g., system evaluators, penetration testers, security control assessors, risk assessors, independent verifiers/validators, inspectors general, auditors). Organizations may explicitly define how established priorities and values guide the identification of high-value assets and the potential adverse impacts to organizational stakeholders. If such information is not defined, priorities and values related to identifying targets of threat sources and associated organizational impacts can typically be derived from strategic planning and policies. For example, security categorization levels indicate the organizational impacts of compromising different types of information."}], "metadata": {"source": "Guide for Conducting Risk Assessments", "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 Recommendation for Random Number Generation Using Deterministic Random Bit Generators provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-90A Revision 1\n\n## Recommendation for Random Number Generation Using Deterministic Random Bit Generators\n\nElaine Barker John Kelsey\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-90Ar1\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-90A Revision 1\n\n## Recommendation for Random Number Generation Using Deterministic Random Bit Generators\n\nElaine Barker John Kelsey\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-90Ar1\n\nJune 2015\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3541 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, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A-130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Recommendation for Random Number Generation Using Deterministic Random Bit Generators", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Attribute Considerations for Access Control Systems:\n\n- Encryption\n- Measures taken to detect unintended alteration of attribute values\n- Data stores on a network behind a proper defense-in-depth posture\n- Policies enforced on the attribute update, copy, revoke, or modify process\n- Logged and audited change of attribute\n\n- Security protocols are used for transmitting both attribute requests and attribute values to the attribute provider or access control function (e.g., transmitting in the clear without encryption versus PKI-enabled TLS sessions). - Replay attack protection is typically accomplished by including information provided by the access control function into the signed message that is provided by the remote access control function or attribute provider. This guarantees the integrity and confidentiality of the attribute. - Transmitted attributes are applied in a multi-tier receipt of attributes (i.e., when attributes are sent by remote access control function or provider such that the assured attribute can be passed through the chain of forwarding routes). For example, for higher levels of assurance, using digitally signed attributes (crypto-binding) provides a hash of the attribute to ensure that it has not been altered or tampered with before it is received."}], "metadata": {"source": "Attribute Considerations 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Security Considerations for Remote Electronic UOCAVA Voting:\n\n.. 4 | 2 GENERAL ARCHITECTURE............................................................ 4 | 2 GENERAL ARCHITECTURE............................................................\n4 |\n| 2.1 | SYSTEM COMPONENTS | ....................................................................4 |\n| 2.2 | AUTHORIZED USERS.......................................................................7 | |\n| 2.3 | THREAT SOURCES..........................................................................8 | |\n| 3 OVERVIEW................................................................................ 12 | 3 OVERVIEW................................................................................ 12 | 3 OVERVIEW................................................................................ 12 |\n| 4 | CONFIDENTIALITY...................................................................."}], "metadata": {"source": "Security Considerations for Remote Electronic UOCAVA Voting", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms:\n\n| 27 | | Appendix E- Supporting NIST SP 800-53 Security Controls and Publications | ...30 | | Appendix F- Cybersecurity Framework Subcategory Mappings..........................32 | | | Appendix G-Acronyms and Other Abbreviations .................................................33 | | | List of Tables | List of Tables | | Table 1: VMs Instantiated on the VMware-Based Management Cluster | .......................21 | | Table 2: VMs Instantiated on the KVM-Based Managed Cluster | ..................................22 | | Table 3: Security Capabilities Provided by the Prototype..............................................30 | | | Table 4: Mapping of Security Capabilities to NIST SP 800-53 Controls........................31 | | | List of Figures | List of Figures | | Figure 1: Concept of Trusted Pools.................................................................................7 | | | Figure 2: Stage 1 Solution Overview...............................................................................8 | | | Figure 3: Stage 3 Solution Architecture.........................................................................10 | | | Figure 4: Stage 4 Solution Architecture.........................................................................13 | | | Figure 5: Prototype Implementation Architecture | ..........................................................15 | | Figure 6: Remote Attestation Protocol...........................................................................17 | | | Figure 7: Prototype Architecture....................................................................................19 | | | Figure 8: MCM Console to Import a Cluster..................................................................23 | | | Figure 9: Managed Cluster Policies...............................................................................24 | | | Figure 10: Creating Pipeline for Image Decryption........................................................26 | | | Figure 11: Sample JWT Created by"}], "metadata": {"source": "Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Research Report_ User Perceptions of Smart Home Privacy and Security:\n\n3.2.3 | Government Access | 15 |\n| | 3. 3.2.3 Government Access\n\nSeveral participants were concerned about national governments gaining access to smart home data, especially audio and video."}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "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 Directions in Security Metrics Research provide? (Part 2)"}, {"role": "assistant", "content": "ndation 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.\n## Abstract\n\nMore than 100 years ago, Lord Kelvin insightfully observed that measurement is vital to deep knowledge and understanding in physical science. During the last few decades, researchers have made various attempts to develop measures and systems of measurement for computer security with varying degrees of success. This paper provides an overview of the security metrics area and looks at possible avenues of research that could be pursued to advance the state of the art. Keywords: Security Metrics; Computer Security, Security Evaluation\n\n## Acknowledgements\n\nThis report received the support of many individuals. The author is grateful to Tim Grance for suggesting the topic and encouraging its development. The author also wishes to thank colleagues who reviewed drafts of this document and contributed to its technical content, as well as the individuals who reviewed the public-release draft of this document and provided comments during the review period. Improvements to the content would not have been possible without their feedback and valuable suggestions. In particular, Paul Black, Lee Badger, and Russell Cameron Thomas offered useful and thought-provoking insight on the subject matter. However, the author takes full responsibility for any remaining errors or omissions in the report. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Directions in Security Metrics Research", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nn the RMF; information resources as system and system elements; authorization boundaries; security and privacy posture; and security and privacy considerations related to supply chain risk management.\n- Chapter Three describes the tasks required to implement the steps in the RMF including: organization-level and information system-level preparation; categorization of information and information systems; control selection, tailoring, and implementation; assessment of control effectiveness; information system and common control authorization; the ongoing monitoring of controls; and maintaining awareness of the security and privacy posture of information systems and the organization. - Supporting Appendices provide additional information and guidance for the application of the RMF including:\n- -References;\n- -Glossary of Terms;\n- -Acronyms;\n- -Roles and Responsibilities;\n- -Summary of RMF Tasks;\n- -System and Common Control Authorizations;\n- -Authorization Boundary Considerations; and\n- -System Life Cycle Considerations."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\nwhich those internal controls are enacted (the 'control environment'), they also perform a risk assessment to identify conditions that may prevent the effective application of those internal controls.\nBusiness managers and system owners select and implement security and privacy control activities (e.g., those described in SP 800-53, Security and Privacy Controls for Information Systems and Organizations ) to achieve the desired objectives and monitor their effectiveness [8]. Fig. 5 illustrates that the terms control , assess , and monitor are used at all three hierarchy levels yet include different activities."}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Introduction to Cybersecurity for Commercial Satellite Operations:\n\nated and maintained. | CM-2, CM-3, CM-4, CM-5, CM-6, CM-7, CM-9, SA-10 | CM-2, CM-3, CM-4, CM-5, CM-6, CM-7, CM-9, SA-10 |\n| | PR.IP-3: Configuration change control processes are in place.\n| CM-3, 4, 10 | CM-3, 4, SA-10 |\n| | PR.IP-9: Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are in place and managed. | PS 2,3,4,5,6,7, CM-7 | CM-7 |\n| | PR.IP-12: A vulnerability management plan is developed and implemented. | RA-1, RA-3, RA- 5, SI-2 | RA-1, RA-3, RA-5, SI-2 |\n| | PR.PT-1: Audit/log records are determined, documented, implemented, and reviewed in accordance with policy. | AU Family | AU1, 2, 3, 6, 7, 12, 13, 14, 16 |\n| | PR.PT-3: The principle of least functionality is incorporated by configuring systems to provide only essential capabilities. | AC-3, 8, 9,19 | AC-3, CM-7 |"}], "metadata": {"source": "Introduction to Cybersecurity for Commercial Satellite Operations", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security Considerations for Voice Over IP Systems provide? (Part 5)"}, {"role": "assistant", "content": "| | | 4 H.323...................................................................................................................................................26 | 4 H.323...................................................................................................................................................26 | 4 H.323...................................................................................................................................................26 | | 4.1 | H.323 Architecture ....................................................................................................................26 | | | 4.2 | H.235 Security Profiles..............................................................................................................28 | | | 4.2.1 | H.235v2..................................................................................................................................29 | | | 4.2.2 | H.235v3..................................................................................................................................32 | | | 4.2.3 | H.323 Annex J .......................................................................................................................36 | | | 4.2.4 | H.323 Security Issues............................................................................................................36 | | | 4.3 | Encryption Issues and Performance..........................................................................................37 | | | 5 SIP.......................................................................................................................................................39 | 5 SIP.......................................................................................................................................................39 | 5 SIP.......................................................................................................................................................39 | | 5.1 | SIP Architecture.........................................................................................................................39 | | | 5.2 Existing Security Features within the SIP Protocol .................................................................40 | 5.2 Existing Security Features within the SIP Protocol .................................................................40 | 5.2 Existing Security Features within the SIP Protocol .................................................................40 | | 5.2.1 | Authentication of Signaling Data using HTTP Digest Authentication...............................41 | | | 5.2.2 | S/MIME Usage within SIP....................................................................................................41 | | | 5.2.3 | Confidentiality of Media Data..............................................................................................41 | | | 5.2.4 5.2.5 | TLS usage within SIP............................................................................................................42 IPsec usage within | SIP..........................................................................................................42 | | 5.2.6 | Security Enhancements for SIP ............................................................................................42 | | | 6 Gateway | 5.2.7 SIP Security Issues ................................................................................................................44 | Decomposition..................................................................................................................47 | | | 6.1 MGCP........................................................................................................................................47 | | | 6.1.1 | Overview................................................................................................................................47 | | \\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_ | 6.1.2 | System Architecture...............................................................................................................48 |"}], "metadata": {"source": "Security Considerations for Voice Over IP Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security Architecture Design Process for Health Information Exchanges (HIEs):\n\nHIPAA Security Rule: 45 CFR 164.312(e)(1), Standard: Transmission Security; Implementation Specification: Encryption.\n\n- SP 800-45, Version 2, Guidelines on Electronic Mail Security.\n- SP 800-52, Guidelines for the Selection and Use of Transport Layer Security (TLS) Implementations.\n- SP 800-53 Rev. 3, Recommended Security Controls for Federal Information Systems and Organizations, security control family: System and Communications Protection (SC).\n- SP 800-58, Security Considerations for Voice Over IP Systems.\n- SP 800-77, Guide to IPsec VPNs.\n- SP 800-113, Guide to SSL VPNs.\n\nIllustration: Hospital One sends health records to Hospital Two. Hospital One sends the document using previously agreed-upon encryption methods to ensure the confidentiality of the exchanged health records."}], "metadata": {"source": "Security Architecture Design Process for Health Information Exchanges (HIEs)", "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 Advanced Encryption Standard (AES):\n\n9. Implementation Schedule. This Standard became effective on May 26, 2002. 10. Patents. Implementations of the algorithm specified in this Standard may be covered by U.S. and foreign patents. 11. Export Control. Certain cryptographic devices and technical data regarding them are subject to federal export controls. Exports of cryptographic modules implementing this Standard and technical data regarding them must comply with all federal laws and regulations and must be licensed by the Bureau of Industry and Security of the U.S. Department of Commerce. Information about export regulations is available at https://www.bis.doc.gov. 12. Qualifications. NIST will continue to follow developments in the analysis of the AES algorithm. As with its other cryptographic algorithm standards, NIST will formally reevaluate this Standard every five years. In 1997, NIST initiated the Advanced Encryption Standard (AES) development effort [1] and called for the public to submit candidate algorithms for block ciphers. Block ciphers are the foundation for many cryptographic services, especially those that provide assurance of the confidentiality of data. In 2000, NIST announced the selection of Rijndael [2, 3] for the AES. - [1] James Nechvatal, Elaine Barker, Lawrence Bassham, William Burr, Morris Dworkin, James Foti, and Edward Roback. Report on the Development of the Advanced Encryption Standard (AES). Journal of Research of NIST (NIST JRES) , May 2001. https://doi.org/10.6028/jres. 106.023. - [2] Joan Daemen and Vincent Rijmen. AES Proposal: Rijndael Document Version 2. AES Algorithm Submission, September 1999. Available at https://csrc.nist.gov/csrc/media/projects/cryptographic-standards-and-guidelines/ documents/aes-development/rijndael-ammended.pdf. - [3] Joan Daemen and Vincent Rijmen. The Design of Rijndael - The Advanced Encryption Standard (AES), Second Edition . Information Security and Cryptography. Springer, 2020. https://doi.org/10.1007/978-3-662-60769-5."}], "metadata": {"source": "Advanced Encryption Standard (AES)", "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.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to An Introduction to Privacy Engineering and Risk Management in Federal Systems:\n\n3.2.2 Privacy Risk Characteristics ... 3.2.2. 3.2.2."}], "metadata": {"source": "An Introduction to Privacy Engineering and Risk Management in Federal 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 does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Security Recommendations for Server-based Hypervisor Platforms:\n\nSince VMs are prime sources of threats to the hypervisor, continuous monitoring of the state of VMs and the traffic going in and out of those VMs is necessary for: (a) controlling the type of traffic, (b) intrusion detection and prevention, and (c) detecting viruses and other malware. This function can be accomplished in two ways:\n\nSecurity Recommendation HY-SR-16: All anti-malware tools (e.g., virus checkers, firewalls, and IDPS) running in the virtualized host should have the capability to perform autonomous signature or reference file updates on a periodic basis. | HY-SR-15 | Solutions for Security Monitoring and security policy enforcement of VMs should be based 'outside of VMs' and should leverage the virtual machine introspection capabilities of the hypervisor. Generally, such solutions involve running a security tool as a Security Virtual Appliance (SVA) in a security-hardened or trusted VM. . | HY-BF4 (VM Lifecycle Management) |\n|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------|\n| HY-SR-16 | All antimalware tools (virus checkers, firewalls and IDPS) running in the virtualized host should have the capability to perform autonomous signature or reference file updates on a periodic basis. | HY-BF4 (VM Lifecycle Management) |\n| HY-SR-17 | VM configuration management tools should have the capability to compile logs and alert administrators when configuration changes are detected in any VM that is being monitored."}], "metadata": {"source": "Security Recommendations for Server-based Hypervisor Platforms", "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 Measuring the Usability and Security of Permuted Passwords on Mobile Platforms:\n\n11 Cryptography: The discipline that embodies principles, means and methods for providing information security, including confidentiality, data integrity, non- repudiation, and authenticity. - [1] K. K. Greene, M. A. Gallagher, B. Stanton, and P. Y. Lee, ' I Can ' t Type That!, P@$$w0rd Entry on Mobile Devices, ' in Human Aspects of Information Security, Privacy, and Trust , Lecture Notes in Computer Science 8533, 2014, pp. 160-171. http://dx.doi.org/10.1007/978-3-319-07620-1\\_15. - [2] M. Jakobsson and R. Akavipat, ' Rethinking Passwords to Adapt to Constrained Keyboards, ' Mobile Security Technologies 2012 (MoST 2012) , San Francisco, California, United States, May 24, 2012. http://www.mostconf.org/2012/papers/5.pdf [accessed 4/19/2016]. - [3] National Strategy for Trusted Identities in Cyberspace, Enhancing Online choice, Efficiency, Security, and Privacy , 2011. http://purl.fdlp.gov/GPO/gpo7204. - [4] B. Stanton and K. Greene, ' Character strings, memory, and passwords: What a recall study can tell us, ' in Human Aspects of Information Security, Privacy, and Trust , Lecture Notes in Computer Science 8533, 2014, pp. 195-206. http://dx.doi.org/10.1007/978-3-319-07620-1\\_18. - [5] International Organization for Standardization, Ergonomic requirements for office work with visual display terminals (VDTs) -- Part 11: Guidance on usability, ISO 9241-11:1998 . - [6] E. Frøkjær, M. Hertzum, and K. Hornbæk, ' Measuring usability: Are effectiveness, efficiency, and satisfaction really correlated? ' in Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI ' 00) , The Hague, The Netherlands, April 1-6, 2000, pp. 345-352. http://dx.doi.org/10.1145/332040.332455. - [7] A. Adams, and M. A. Sasse, ' Users are not the enemy, ' Communications of the ACM , vol. 42, no. 12 (December 1999), pp 40-46. http://dx.doi.org/10.1145/322796.322806. - [8] D. Florêncio, C. Herley, and P. C."}], "metadata": {"source": "Measuring the Usability and Security of Permuted Passwords on Mobile Platforms", "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 Guide to Protecting the Confidentiality of Personally Identifiable Information (PII):\n\ntential impact is LOW if the loss of confidentiality, integrity, or availability could be expected to have a limited adverse effect on organizational operations, organizational assets, or individuals.\nA limited adverse effect means that, for example, the loss of confidentiality, integrity, or availability might (i) cause a degradation in mission capability to an extent and duration that the organization is able to perform its primary functions, but the effectiveness of the functions is noticeably reduced; (ii) result in minor damage to organizational assets; (iii) result in minor financial loss; or (iv) result in minor harm to individuals."}], "metadata": {"source": "Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1:\n\n3.4.4. 3.4.4. 3.4.4."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1", "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Guidelines for Securing Radio Frequency Identification (RFID) Systems:\n\n----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|\n| 1.\n| 1.1 | Authority...................................................................................................................1-1 | |\n| | 1.2 | Purpose and Scope .................................................................................................1-1 | |\n| | 1.3 | Document Structure.................................................................................................1-2 | |\n| 2."}], "metadata": {"source": "Guidelines for Securing Radio Frequency Identification (RFID) Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Media Protection?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n| Identify, document, and report vulnerabilities that exist on the PNT system and the system that distributes PNT data. Where safe and feasible, include the use of vulnerability scanning on the PNT system, its components, or a representative system. Testing and characterization to assess system vulnerabilities are recommended periodically or when there are changes to the threat model, the organization's reliance on PNT data, or modifications to the PNT equipment. Receiver or system vulnerability testing may include PNT signal simulation to assess susceptibility to disruption or manipulation of the PNT signal. Testing should be conducted in accordance with industry best practices, laws, and regulations as well as within the business continuity constraints defined for the organization. Vulnerabilities for an operational environment may include the susceptibility to atmospheric and scintillation effects on PNT signals, spoofing of unauthenticated signals, or disruptions or manipulations of PNT services. | DHS CISA 4.a DHS GPS CI ICAO 9849 5, 7.13 IEEE 2030.101 4.12, 4.14, 5 NIST SP 800-53 Rev. 5 CA-2, CA-7, CA-8, PM-15, RA-3, RA-5, SA-5, SA-11, SI-2, SI- 4, SI-5 NTP SEC RTCA 229 1.6.2, 2, 2.1.1.1.4, 2.1.1.1.5, 2.4, 2.5 RTCA 356 3.8.1, 3.8.2 USG FRP 1.7.3 |"}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\nignatures on Authentication Information |\n| DTR-07.03.01.02 | If RSA with PSS padding is used, the parameters field of the AlgorithmIdentifier type shall assert SHA-256 (OID = 2.16.840.1.101.3.4.2.1).\nFor RSA with PKCS #1 v1.5 padding, the parameters field is populated with NULL. For ECDSA, the parameters field is absent. | • [PROF], Worksheet titled - Derived PIV Authentication Certificate Profile |\n| DTR-07.03.01.03 | The subjectPublicKeyInfo field shall assert an algorithm in the AlgorithmIdentifier in accordance with Table 3-4 of [SP800-78]. | • [SP800-78], Section 3.2.2 - Specification of Public Keys In X.509 Certificates |\n| DTR-07.03.01.04 | If the public key algorithm is elliptic curve, then the parameters field contains the namedCurve choice populated with the OID for Curve P-256 (1.2.840.10045.3.1.7). | • [PROF], Worksheet titled - Derived PIV Authentication Certificate Profile |\n| DTR-07.03.01.05 | The keyUsage extension shall assert only the digitalSignature bit. No other bits shall be asserted. | • [PROF], Worksheet titled - Derived PIV Authentication Certificate Profile |\n| DTR-07.03.01.06 | The policyIdentifier field in the certificatePolicies must assert id-fpki- | • [PROF], Worksheet titled - Derived PIV |"}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4):\n\n3.2.3 |\n| SER5 | A TPDU with an improper label shall be discarded. 3.2.3 | Local Matter; Audit Advised."}], "metadata": {"source": "Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4)", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\nenterprise mobility management (EMM); mobile; mobile application vetting (MAV); mobile device management (MDM); mobile security; mobile threat defense (MTD); tablets. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| | Introduction ...................................................................................................................... | 2 |\n| | Purpose......................................................................................................................"}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "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 Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1:\n\n| Update | Description of Update |\n|-----------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Clarified that terms like 'compliance' can be confusing and mean something very different to various Framework stakeholders | Added clarity that the Framework has utility as a structure and language for organizing and expressing compliance with an organization's own cybersecurity requirements. However, the variety of ways in which the Framework can be used by an organization means that phrases like 'compliance with the Framework' can be confusing."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\n| | Executive Summary..................................................................................................... | Executive Summary..................................................................................................... | iv |\n|----|----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------|\n| 1 | Introduction............................................................................................................ | Introduction............................................................................................................"}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MP.L2-3.8.3 (NIST 3.8.3)?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n3.8.3, 3."}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "nist_control": "3.8.3", "cmmc_practice_id": "MP.L2-3.8.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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Secure Domain Name System (DNS) Deployment Guide:\n\nDNS software should not be running or present in hosts that are not designated as name servers. The possibility arises in the case of DNS BIND software because of the fact that many versions of Unix (including Solaris and Linux versions) come installed with BIND as default. Hence, while taking an inventory of software in workstations and servers of the enterprise as part of the security audit, it is necessary to look for BIND installations and remove them from hosts that are not functioning as name servers."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment 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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\n\n- Intel Control-Flow Enforcement Technology (Intel CET)\n- Arm Pointer Authentication Code (PAC)\n- Arm Branch Target Identification (BTI)\n- IBM ROP and COP/JOP Attack Defenses\n\nA trusted execution environment (TEE) is an area or enclave protected by a system processor. Sensitive secrets like cryptographic keys, authentication strings, or data with intellectual property and privacy concerns can be preserved within a TEE, and operations involving these secrets can be performed within the TEE, thereby eliminating the need to extract the secrets outside of the TEE. A TEE also helps ensure that operations performed within it and the associated data cannot be viewed from outside, not even by privileged software or debuggers. Communication with the TEE is designed to only be possible through designated interfaces, and it is the responsibility of the TEE designer/developer to define these interfaces appropriately. A good TEE interface limits access to the bare minimum required to perform the task. - https://www.amd.com/system/files/TechDocs/SEV-SNP-strengthening-vm-isolationwith-integrity-protection-and-more.pdf\n- [47] Arm (2022) Arm Architecture Reference Manual for A-profile architecture . Available at https://developer.arm.com/documentation/ddi0487/latest\n- [48] Arm (2020) Trusted Base System Architecture for Armv8-A . Available at https://developer.arm.com/documentation/den0021/f/?lang=en\n- [49] Arm (2022) TrustZone for AArch64 . Available at https://developer.arm.com/documentation/102418/0100/What-is-TrustZone-?lang=en\n- [50] Parsec Project (2022) Parsec. Available at https://github.com/parallaxsecond/parsec\n- [51] Parsec Project (2019) Authenticators . Available at https://parallaxsecond.github.io/parsec-book/parsec\\_service/authenticators.html\n- [52] SPIFFE (2022) SPIFFE Verifiable Identity Document (SVID) . Available at https://spiffe.io/docs/latest/spiffe-about/spiffe-concepts/#spiffe-verifiable-identitydocument-svid\n- [53] SPIFFE (2022) SPIRE Concepts ."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cryptographic Algorithms and Key Sizes for Personal Identity Verification:\n\nSpecification of Digital Signatures on Authentication Information..........................................7 | 3.2.1. Specification of Digital Signatures on Authentication Information..........................................7 | |\n| | 3.2.2. Specification of Public Keys In X.509 Certificates .....................................................................8 | 3.2.2. Specification of Public Keys In X.509 Certificates .....................................................................8 | |\n| | 3.2.3."}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series:\n\neakdown in security, which is similar to the reuse of a one-time pad. Files of more than 64 GiB are not unusual in video editing and genomics research, but they cannot be encrypted using the GCM mode.\nFor example, the Cryfa [38][72] tool to encrypt genomic data suggests using the command line tool 'split' to handle files of more than 64 GiB (and the 'cat' command line tool to rejoin the parts after decryption), a cumbersome process that could have been avoided if GCM supported larger plaintexts. NIST's Galois/Counter Mode (GCM) and GMAC Validation System (GCMVS) [48] also contain tests for testing for GCM-AES-XPN, where 'XPN' is an abbreviation of 'eXtended Packet Numbering.' GCM-AES-XPN is used in IEEE 802.1AE, also known as MACsec [41]. The only difference with GCM is that there is an additional salt input, which is XORed with the IV input to create the nonce for GCM. The rationale for the salt input of GCM-AES-XPN is to mitigate the concern that 'counter mode gives an attacker exactly what they want for integral cryptanalysis: a complete set of block cipher inputs that differ only in some bit positions' [54]. This is an incorrect understanding of the security of block cipher modes of operation and of the AES block cipher. The security model assumes that the adversary can query plaintexts of its choosing. However, care must now be taken that no additional vulnerability is introduced by GCM-AES-XPN: rather than ensuring the uniqueness of the nonce, the uniqueness of the XOR of the IV and the salt must be ensured. Similarly, Cryfa shuffles the plaintext before the GCM encryption is applied in an unnecessary attempt to mitigate known-plaintext attacks. Lastly, note that in the multi-key security [56] setting where cryptographic algorithms are used"}], "metadata": {"source": "Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\n|\n| Table 1.\nTechnical cybersecurity capability recommendations...........................................................14 |\n| Table 2. Non-technical cybersecurity capability recommendations....................................................19 |\n| Table 3. Characteristics of tested inverters .......................................................................................28 |\n| Table 4. Guideline #1 testing results .................................................................................................28 |\n| Table 5. Guideline #2 testing results .................................................................................................29 |\n| Table 6. Guideline #3 testing results .................................................................................................29 |\n| Table 7. Guideline #4 testing results .................................................................................................30 |\n| Table 8."}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to BIOS Protection Guidelines for Servers:\n\n.................................................................. | 1. Introduction....................................................................................................................\n| 1-1 |\n| 1.1 | Purpose and Scope................................................................................................1-1 | |\n| 1.2 | Audience | ................................................................................................................1-1 |\n| 1.3 | Document Structure................................................................................................1-2 | |\n| 2. Background.................................................................................................................... 2-1 | 2. Background.................................................................................................................... 2-1 | 2. Background...................................................................................................................."}], "metadata": {"source": "BIOS Protection Guidelines for Servers", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Information Security Guide for Government Executives:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) has the broad mission of supporting U.S. industry, government, and academia by promoting U.S. innovation and industrial competitiveness through advancement of information technology measurement science, standards, and technology in ways that enhance economic security and improve our quality of life. ITL researchers have developed detailed protocols and operational standards that improve safety of their operation, and established assessment criteria and test data sets for validation of industrial products. ITL formulates metrics, tests, and tools for a wide range of subjects such as information complexity and comprehension, high confidence software, space-time coordinated mobile and wireless computing, as well as, issues of information quality, integrity, and usability. Under the Federal Information Security Management Act, ITL is directed to develop cyber security standards, guidelines, and associated methods and techniques. ITL responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of non national-security-related information in federal information systems. This Interagency Report provides a broad overview of information security program concepts to assist senior leaders in understanding how to oversee and support the development and implementation of information security programs."}], "metadata": {"source": "Information Security Guide for Government Executives", "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 Computer Security Division 2004 Annual Report:\n\ne civil service, the senior executive service, the military, some of the largest corporations worldwide, small- and medium-sized businesses and some of the top universities in the nation.\nThe members' experience likewise covers a broad spectrum of activities including many different engineering disciplines, computer programming, systems analysis, mathematics, management positions, information technology auditing, legal experience (two Board members are attorneys), an extensive history of professional publications and professional journalism. Members have worked (and in many cases, are continuing to work in their fulltime jobs) on the development and evolution of some of the most important pieces of information security and privacy in the Federal government, including the Privacy Act of 1974, the Computer Security Act of 1987, the Federal Public Key Infrastructure (PKI) effort and numerous egovernment services and initiatives."}], "metadata": {"source": "Computer Security Division 2004 Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing 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. Computer security; Cybersecurity Framework (CSF); distributed control systems (DCS); industrial control systems (ICS); information security; manufacturing; network security; programmable logic controllers (PLC); risk management; security controls; supervisory control and data acquisition (SCADA) systems\n\n| 1. Introduction ............................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 Purpose & Scope............................................................................................ 1 |\n| 1.2 Audience......................................................................................................... 2 |\n| 1.3 Document Structure........................................................................................ 2 2."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide for Cybersecurity Event Recovery:\n\n| Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi |\n|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction .........................................................................................................................1 | 1. Introduction .........................................................................................................................1 | 1."}], "metadata": {"source": "Guide for Cybersecurity Event Recovery", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide to LTE Security:\n\nhich components are infected. These types of attacks have been previously observed in GSM networks [22], but as of this time there is no known example of this attack within backend LTE infrastructure.\nA Distributed Denial of Service (DDoS) attack against an MME could be launched via a continuous stream of attach requests."}], "metadata": {"source": "Guide to LTE Security", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Digital Signature Standard (DSS):\n\nThis standard specifies a suite of algorithms that can be used to generate a digital signature. Digital signatures are used to detect unauthorized modifications to data and to authenticate the identity of the signatory. In addition, the recipient of signed data can use a digital signature as evidence in demonstrating to a third party that the signature was, in fact, generated by the claimed signatory. This is known as non-repudiation since the signatory cannot easily repudiate the signature at a later time. 3. Explanation : This standard specifies algorithms for applications requiring a digital signature rather than a written signature. A digital signature is represented in a computer as a string of bits and computed using a set of rules and parameters that allow the identity of the signatory and the integrity of the data to be verified. Digital signatures may be generated on both stored and transmitted data. 4. Approving Authority: Secretary of Commerce. 5. Maintenance Agency: Department of Commerce, National Institute of Standards and Technology, Information Technology Laboratory, Computer Security Division. 6. Applicability: This standard is applicable to all federal departments and agencies for the protection of sensitive unclassified information that is not subject to section 2315 of Title 10, United States Code, or section 3502 (2) of Title 44, United States Code. This standard shall be used in designing and implementing public key-based signature systems that federal departments and agencies operate or that are operated for them under contract. The adoption and use of this standard are available to private and commercial organizations. 7. Applications: A digital signature algorithm allows an entity to authenticate the integrity of signed data and the identity of the signatory."}], "metadata": {"source": "Digital Signature Standard (DSS)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommended Criteria for Cybersecurity Labeling of Consumer Software:\n\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|\n| | 1.1 Background..................................................................................................... | 1 |\n| 1.2 | Document Scope and Goals........................................................................... | 1 |\n| 1.3 | Labeling Schemes and Scheme Owners........................................................"}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling of Consumer Software", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Asset Management:\n\nld allow installation or execution. |\n| 3) Gain Foothold | The attacker has gained entry to the assessment object and achieves enough compromise to gain a foothold, but without persistence.\nExamples include: unauthorized user successfully logs in with authorized credentials; browser exploit code successfully executed in memory and initiates call back; person gains unauthorized access to server room. | Block Foothold: Reduce number of devices susceptible to compromise due to unauthorized software being allowed to execute. |\n| 4) Gain Persistence | The attack has gained a foothold on the object and now achieves persistence. Examples include: malware installed on host that survives reboot or log off; basic input/output system (BIOS) or kernel modified; new/privileged account created for unauthorized user; unauthorized person issued credentials/allowed access; unauthorized personnel added to access control list (ACL) for server room. | Block Persistence/Prevent: Stop or delay compromise of devices by restricting software installation. Block Persistence/Detect: Reduce amount of time that malicious or compromised software is installed or remains active before detection and removal. |\n| 6) Achieve Attack Objective | The attacker achieves an objective. Loss of confidentiality, integrity, or availability of data or system capability. Examples include: exfiltration of files; modification of database entries; deletion of file or application; denial of service; disclosure of personally identifiable information (PII). | Restore required and authorized software as needed, after being removed or altered by attackers, contingency (disk failure), or by mistake. |"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does User's Guide to Telework and Bring Your Own Device (BYOD) Security provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-114 Revision 1\n\n## User's Guide to Telework and Bring Your Own Device (BYOD) Security\n\nMurugiah Souppaya Karen Scarfone\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-114r1\n\nC O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-114 Revision 1\n\n## User's Guide to Telework and Bring Your Own Device (BYOD) Security\n\nMurugiah Souppaya Computer Security Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-114r1\n\nJuly 2016\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3541 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."}], "metadata": {"source": "User's Guide to Telework and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management:\n\n| Example Enterprise Type | Example Risk Appetite Statement | Example Risk Tolerance Statement |\n|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Global Retail Firm | Our customers associate reliability with our company's performance, so service disruptions must be minimized for any customer-facing websites. | Regional managers may permit website outages lasting up to 4 hours for no more than 5 %of its customers. |\n| Government Agency | Mission-critical systems must be protected from known cybersecurity vulnerabilities. | Systems designated as mission-critical must be patched against critical software vulnerabilities (severity score of 10) within 14 days of discovery. |\n| Internet Service Provider | The company has a low risk appetite with regard to failure to meet customer service level agreements, including network availability and communication speeds."}], "metadata": {"source": "Identifying and Estimating Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Cryptographic Key Generation:\n\n| Algorithm | A clearly specified mathematical process for computation; a set of rules that, if followed, will give a prescribed result. |\n|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Approved | FIPS-approved and/or NIST-recommended. |\n| Asymmetric key | A cryptographic key used with an asymmetric-key (public-key) algorithm. The key may be a private key or a public key. |\n| Asymmetric-key algorithm | Acryptographic algorithm that uses two related keys: a public key and a private key. The two keys have the property that determining the private key from the public key is computationally infeasible; also known as a public-key algorithm. |\n| Bit string | An ordered sequence of 0 and 1 bits. |\n| Ciphertext | Data in its encrypted form. |\n| Compromise | The unauthorized disclosure, modification, or use of sensitive data (e.g., keying material and other security-related information). |\n| Cryptographic algorithm | A well-defined computational procedure that takes variable inputs (often including a cryptographic key) and produces an output. |\n| Cryptographic boundary | An explicitly defined continuous perimeter that establishes the physical bounds of a cryptographic module and contains all the hardware, software, and/or firmware components of a cryptographic module. See FIPS 140."}], "metadata": {"source": "Recommendation for Cryptographic Key Generation", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products:\n\nCybersecurity utility: Maintaining confidentiality, integrity, and availability of data is foundational to cybersecurity for IoT products. Customers will expect that data is protected and that protection of data helps to ensure safe and intended functionality of the IoT product. Cybersecurity utility: Inventorying 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."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "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 An Industrial Control System Cybersecurity Performance Testbed provide? (Part 2)"}, {"role": "assistant", "content": "Department of Commerce Penny Pritzker, Secretary National Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director ## Table of Contents | | Introduction ..........................................................................................................................................1 | Introduction ..........................................................................................................................................1 | |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| | | Testbed Design Approach.....................................................................................................................2 | Testbed Design Approach.....................................................................................................................2 | | 3 | Testbed Design......................................................................................................................................3 | Testbed Design......................................................................................................................................3 | | 3.1 | Tennessee Eastman Process .........................................................................................................3 | Tennessee Eastman Process .........................................................................................................3 | | 3.1.1 | Tennessee Eastman Process: Analog Simulation..................................................................3 | Tennessee Eastman Process: Analog Simulation..................................................................3 | | 3.1.1.1 | Tennessee Eastman Process: C++ Derivative....................................................................5 | Tennessee Eastman Process: C++ Derivative....................................................................5 | | 3.1.2 | Testbed Enclave: Hardware-in-the-Loop Simulator..............................................................5 | Testbed Enclave: Hardware-in-the-Loop Simulator..............................................................5 | | 3.1.2.1 | Logical Architecture ..........................................................................................................5 | Logical Architecture ..........................................................................................................5 | | 3.1.2.2 | Physical Architecture ........................................................................................................7 | Physical Architecture ........................................................................................................7 | | 3.1.2.3 | TE Plant Software Architecture.........................................................................................7 | TE Plant Software Architecture.........................................................................................7 | | 3.1.2.4 | TE Controller Software Architecture.................................................................................8 | TE Controller Software Architecture.................................................................................8 | | 3.1.2.5 | Theory of Operation..........................................................................................................9 | Theory of Operation..........................................................................................................9 | | 3.1.3 | Process Control with Faster Dynamics..................................................................................9 | Process Control with Faster Dynamics..................................................................................9 | | 3.2.1 | Computing Rack Design ......................................................................................................11 | Computing Rack Design ......................................................................................................11 | |"}], "metadata": {"source": "An Industrial Control System Cybersecurity Performance Testbed", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Guidelines for Derived Personal Identity Verification (PIV) Credentials:\n\n3.3.3 of [SP800-73Part1] except for the following:\n- o References to ' keysWithOnCardCerts ' should be interpreted as keys for which the corresponding certificate is populated within the Derived PIV Application."}], "metadata": {"source": "Guidelines for Derived Personal Identity Verification (PIV) Credentials", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\n3.3.1 | Data Recording | 3-13 |\n| | | 3. 3.3.1 Data Recording\n\nAudit data is recorded from several sources (such as the logon host's operating system or a remote application) to produce a complete picture of a user's security relevant actions."}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating Systems", "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 Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop provide? (Part 2)"}, {"role": "assistant", "content": "ory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications.\nThus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nThis report provides a summary of the discussion and findings from the NIST Cybersecurity Risks in Consumer Home Internet of Things (IoT) Devices virtual workshop in October 2020."}], "metadata": {"source": "Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Program Review for Information Security Management Assistance (PRISMA):\n\nthe information security program and the agency's ability to comply with existing requirements in eight areas . The last TA reviews the technical aspects of the overall information security program .\nPRISMA therefore provides a framework to assist in instructional purposes as well as to assist assessments, independent evaluations, or reviews."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\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. Storage, computing, and networking form the three fundamental building blocks of an information technology infrastructure. Just like computing and network technologies, storage technology has also evolved over the years. Higher capacity storage media and storage system architecture are the two fronts on which storage technology has evolved."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "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 IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\ndurable housing may be needed to withstand excessive heat, cold, and moisture while still providing data availability and integrity. 2. Does the IoT device lack key device cybersecurity requirements?\nKey device cybersecurity requirements are those the organization has determined that the IoT device must possess in order for the device to be integrated in the system and make external connections to other systems or the Internet. Lack of key device cybersecurity requirements indicates that the IoT device cannot support existing information system controls, which subsequently introduces unacceptable levels of risk 16 . To support information system security controls, the organization may need to consider if other system elements (e.g., a gateway, hub, cloud service) can provide the capabilities missing from the IoT device but should keep in mind those key device cybersecurity requirements"}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Managing the Security of Mobile Devices in the Enterprise provide? (Part 5)"}, {"role": "assistant", "content": "osure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| | Introduction ......................................................................................................................"}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n....................................................................................... | 63 |\n| A.1.1.\nC-SCRM Controls Summary........................................................................................................63 | |\n| A.1.1.1. C-SCRM Controls Throughout the Enterprise.......................................................................64 | |\n| A.1.2. Selecting, Tailoring, and Implementing C-SCRM Security Controls ...........................................67 | |\n| A.2.3. FAMILY: ACCESS CONTROL.........................................................................................................69 | |\n| A.2.4. FAMILY: AWARENESS AND TRAINING........................................................................................76 | |\n| A.2.5. FAMILY: AUDIT AND ACCOUNTABILITY......................................................................................79 | |\n| A.2.6. FAMILY: ASSESSMENT, AUTHORIZATION, AND MONITORING..................................................84 | |\n| A.2.7."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Federation and Assertions 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. ## 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": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 U.S. Department of Energy Risk Assessment Methodology provide? (Part 3)"}, {"role": "assistant", "content": "fb'-o^\\,Txst;;,&\n\n•<^3\n\nV'\n\n-miftitSS\n\n.\"A :.,,«\n\n'\n\n,\n\n1\n\n. r\n\ni'-\n\n>'\n\n'\n\n-;Oof\n\ny\n\noj\n\n/\n\n•':\n\nbfi6\n\n>'<r\n\nO':\n\nV 0-r b'Y6ge''\n\n-yy y'r^)T,o3\n\na y\n\nI.H\n\n..-fcra\n\n-\n\ny;\n\n'r\n\n•\n\n'/i'.\n{\n\n;\n\n^\n\n,\n\n^\n\n'\n\n## DEPARTMENT OF ENERGY\n\n\n\n## VOLUME I\n\nDOE RISK ASSESSMENT GUTOELDVE EVSTRUCTIONS, RESOURCE TABLE, AND COMPLETED SAMPLE\n\n- - A Structured Approach - -\n\nSeptember, 1989\n\n## TABLE OF CONTENTS\n\n| | | Page Number | |\n|-------------------------|------------|---------------|----|\n| | | 1 | |\n| INTRODUCTION | | | |\n| 1 . | Background | 1 | |\n| | 2. | | |\n| Objectives Organization | | 2 | |\n| | 3. | 3 | |\n| 4. | | 4 | |\n| | STEP | | |\n| | | 12 | |\n| | | 17 18 | |\n| | | 20 | |\n| | R1 | | |\n| | STEP | 22 | |\n| | | 24 | |\n| | | 26 | |\n| | | 27 | |\n| STEP | | | |\n| | | 29 | |\n| | R3 | | |\n| | | 34 | |\n| STEP | | | |\n| 4 REVIEW ANY | | 37 | |\n| | ."}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\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\nFederal agencies and their contractors are required to select appropriate [FIPS 199] impact levels for their information and to select security controls from those identified in [SP 80053] to use in procurements, implementations and planning. After selecting the applicable security control(s), organizations can initiate the tailoring process to appropriately modify and align the controls more closely with the specific conditions within the organization (i.e., conditions related to organizational missions/business functions, information systems, or environments of operation). This Profile addresses the selection of several of the security controls specified in [SP 800-53], indicating the minimum requirements for those security"}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to BowTie – A deep learning feedforward neural network for sentiment analysis:\n\nThird, what dataset should be used for training? In all cases the size of the training dataset is very important for the quality of training but the way the dataset is constructed and the amount of meta-data it includes also play a role. For example, the Keras IMDB Movie reviews Dataset [10] (KID) for sentiment classification contains human-written movie reviews. A larger dataset of similar type is the Stanford Large Movie Review Dataset (SLMRD) [1]. I consider KID and SLMRD in detail in Sections 1.3 and 1.4. Generally, simpler encodings and models trained on large amounts of data tend to outperform complex systems trained on smaller datasets [13].\n\nFourth, what kind of training procedure should be employed - supervised or unsupervised? Traditionally, NLP systems are trained on large unsupervised corpora and then applied on new data. However, researchers have been able to leverage the advantages of supervised learning and transfer trained models to new data by retaining the transfer accuracy [4].\n\nFifth, when training a model for transfer to other datasets, what are the model characterizing features that guarantee maintaining high/comparable transfer accuracy on the new dataset? Certainly, training and validation accuracy are important but so are the training and validation losses. Some researchers argue that the gradient descent method has an implicit bias that is not yet fully understood, especially in cases where there are multiple solutions that properly classify a given dataset [14]. Thus, it is important to have a neural network with low loss estimates for a trained model to hope for a good and reliable transfer accuracy."}], "metadata": {"source": "BowTie – A deep learning feedforward neural network for sentiment analysis", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendations for Key-Encapsulation Mechanisms:\n\n3.1. Compliance With NIST Standards and Validation . . . . . . . . . . . . . . . .\n\n3.1. Compliance With NIST Standards and Validation"}], "metadata": {"source": "Recommendations for Key-Encapsulation Mechanisms", "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 Case Studies in Cyber Supply Chain Risk Management_ Seagate Technology:\n\nsk management (CSCRM). Managing risks across a large number of diverse suppliers necessitates a clear, scalable, and defensible foundation. Seagate achieves this by leveraging international standards.\n- Internal alignment streamlines incident management. Supply chain incident response requires cross-organizational cooperation. Seagate eliminates friction between disparate functional teams by aligning incident management processes and procedures across all security and risk teams. - Continuous improvement. C-SCRM processes must rapidly incorporate information about new hardware and software vulnerabilities. Seagate leverages open-source intelligence, cross-functional tabletop exercises, and post-incident reporting to improve their incident management practices. - Suppliers welcome C-SCRM support. Many suppliers now recognize the value of robust cybersecurity and supply chain risk management programs. Seagate finds that most suppliers are happy to work together to mature their internal practices."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Seagate Technology", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio:\n\nThe information and communications technology (ICT) on which an enterprise relies is managed through a broad set of ICT risk disciplines that include privacy, supply chain, and cybersecurity. ICT includes a broad range of information and technology that extends far beyond traditional information technology considerations. For example, a growing number of enterprises rely on operational technology (OT) and IoT (Internet of Things) devices' sensors or actuators bridging the physical world and the digital world. Increasingly, artificial intelligence (AI) factors into enterprise risk. NIST's AI Risk Management Framework points out that 'AI risk management should be integrated and incorporated into broader enterprise risk management strategies and processes. Treating AI risks along with other critical risks, such as cybersecurity and privacy, will yield a more integrated outcome and organizational efficiencies.' 1\n\nThis publication addresses OMB's points above for ensuring that ERM considerations and decisions take an ICT portfolio perspective. This publication examines the relationships among ICT risk disciplines and enterprise risk practices. Notably, OMB has stressed the need for enterprise risk considerations and decisions to be based on a portfolio-wide perspective. Individual risk programs have an important role and must integrate activities as part of that enterprise portfolio. Doing so ensures a focus on achieving enterprise objectives and helps identify those risks that will have the most significant impact on the entity's mission. This publication extends that NIST risk program guidance to recognize that risk extends beyond the boundaries of individual programs. There are extensive ICT risk considerations (e.g., Internet of Things, supply chain, privacy, cybersecurity) as well as risk management frameworks that support the management of a mosaic of interrelated risks."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "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 Incident Response?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n| ID | Object Identifier | Description |\n|-----------------------------|----------------------|-------------------------------------------------------------------------------------------------------------|\n| id-PIV- CHUIDSecurityObject | 2.16.840.1.101.3.6.1 | The associated content is the concatenated contents of the CHUID, excluding the asymmetric signature field. |\n| id-PIV- biometricObject | 2.16.840.1.101.3.6.2 | The associated content is the concatenated CBEFF_HEADER + STD_BIOMETRIC_RECORD . |\n\n| ID | Object Identifier | Description |\n|---------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| pivCardholder- Name | 2.16.840.1.101.3.6.3 | The attribute value is of type DirectoryString and specifies the PIV cardholder's name. |\n| pivCardholder-DN | 2.16.840.1.101.3.6.4 | The attribute value is an X.501 type Name and specifies the DN associated with the PIV cardholder in the PIV certificates."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management:\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 systems. The authors, Kelley Dempsey of the National Institute of Standards and Technology (NIST), Dr. George Moore of the Applied Physics Laboratory at Johns Hopkins University, and Paul Eavy of the Department of Homeland Security, wish to thank their colleagues who reviewed drafts of this document, including Nathan Aileo, Nadya Bartol, Craig Chase, Ann Dixon, Terry Fletcher, Jim Foti, John Groenveld, Susan Hansche, Alicia Jones, Amy Heydman, Elizabeth Lennon, Jaime Miller, Susan Pagan, Daniel Portwood, Ron Ross, Martin Stanley, Kevin Stine, Robin Walker, David Waltermire, Kimberly Watson, and Jim Wiggins ."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset 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 Access Control?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program:\n\n| 1. Introduction...................................................................................................................................1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Fundamentals ................................................................................................................................3 |\n| 2.4.1. Chief Executive Officer/Agency Head...........................................................................................6 |\n| 2.4.2. Chief Information Officer .............................................................................................................7 |\n| 2.4.3. Chief Information Security Officer ...............................................................................................7 |\n| 2.4.4. Program Managers and System Owners......................................................................................8 |\n| 2.4.5."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop provide? (Part 4)"}, {"role": "assistant", "content": "This publication may also help IoT device customers or integrators who are incorporating IoT devices intended for the home market into their residence or business, especially small business networks.\n## Acknowledgments\n\nThe authors wish to thank all contributors to this publication, including the participants in this workshop and other interactive sessions; the individuals and organizations from the public and private sectors, including manufacturers for various sectors and several manufacturer trade organizations who provided feedback on the preliminary public content; and colleagues at NIST, The MITRE Corporation, and Scarfone Cybersecurity who offered invaluable input and expertise. ## Table of Contents\n\n| 1 | Introduction ............................................................................................................1 |\n|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Workshop................................................................................................................"}], "metadata": {"source": "Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Operational Technology (OT) Security:\n\nKeith Stouffer\nMichael Pease\nCheeYee Tang\nTimothy Zimmerman\nSmart Connected Systems Division\nCommunications Technology Laboratory\n\n6.2.9. Wireless Communications ..................................................................................... 120\n\n6.4.2. Response Communications (RS.CO) .................................................................... 134"}], "metadata": {"source": "Guide to Operational Technology (OT) 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 additional guidance does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices provide? (Part 2)"}, {"role": "assistant", "content": "en developed by the National Institute of Standards and Technology (NIST) to further its statutory responsibilities under the Federal Information Security Management Act (FISMA) of 2002, P.L. 107-347.\nNIST is responsible for developing standards and guidelines, including minimum requirements, for providing adequate information security for all agency operations and assets, but such standards and guidelines shall not apply to national security systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems, as analyzed in A-130, Appendix IV: Analysis of Key Sections. Supplemental information is provided in A-130, Appendix III. This guideline has been prepared for use by federal agencies. It may also 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. NIST Special Publication 800-60 Volume II, Revision 1, 304 pages\n\n(Date) CODEN: NSPUE2\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by 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."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis:\n\nThe Testbed LAN has three machines: a probe server, source control management (SCM) server, and Network Time Protocol (NTP) and Precision Time Protocol (PTP) capable master clock. The probe server ('ORION') consumes and records network traffic from twelve independent network interfaces. The SCM server ('RIGEL') runs a GitLab server to track and maintain the code used on the enclave, primarily robot code, PLC code, and analysis tools. The NTP/PTP clock ('GEORGE') provides stable time to the enclave servers and systems to enable synchronized logging."}], "metadata": {"source": "Metrics and Key Performance Indicators for Robotic Cybersecurity Performance Analysis", "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 Guidelines on Firewalls and Firewall Policy provide? (Part 5)"}, {"role": "assistant", "content": "| Overview of Firewall Technologies ................................................................................2-1 | Overview of Firewall Technologies ................................................................................2-1 | | | | Firewall Technologies ..............................................................................................2-2 | Firewall Technologies ..............................................................................................2-2 | | | 2.1 | 2.1.1 | Packet Filtering.............................................................................................2-2 | | | | 2.1.2 | Stateful Inspection........................................................................................2-4 | | | | 2.1.3 | Application Firewalls.....................................................................................2-5 | | | | 2.1.4 | Application-Proxy Gateways.........................................................................2-6 | | | | 2.1.5 | Dedicated Proxy Servers..............................................................................2-6 | | | | 2.1.6 | Virtual Private Networking | ............................................................................2-7 | | | 2.1.7 | Network Access Control ...............................................................................2-8 | | | | 2.1.8 | Unified Threat Management (UTM)..............................................................2-9 | | | | 2.1.9 | Web Application Firewalls | ............................................................................2-9 | | | 2.1.10 | Firewalls for Virtual Infrastructures | ...............................................................2-9 | | | 2.2 | Firewalls for Individual Hosts and Home Networks................................................2-10 | | | | | 2.2.1 Host-Based Firewalls and Personal Firewalls ............................................2-10 | | | | 2.2.2 | Personal Firewall Appliances .....................................................................2-11 | | | | 2.3 | Limitations of Firewall Inspection...........................................................................2-11 | | | | Summary of Recommendations.............................................................................2-12 | Summary of Recommendations.............................................................................2-12 | | | 3."}], "metadata": {"source": "Guidelines on Firewalls and Firewall Policy", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Managing Information Security Risk_ Organization, Mission, and Information System View:\n\nthe third option is limited by the ability of organizations to detect potential insertion of malware into the hardware, firmware, or software. As such, it is the least effective of the three options.\nFrom a cost perspective, the first option is potentially the most expensive, depending upon the number of travelers (hence number of travel laptops) required. The second and third options are considerably less expensive. From a mission and operational perspective, the third option is the best alternative as users have access to standard laptop configurations including all applications and supporting data needed to perform tasks supporting missions and business functions. Such applications and data would not be available if the first or second option is selected. Ultimately, the evaluation of courses of action is made based on operational requirements, including information security requirements, needed for near and long term mission/business success. Budgetary constraints, consistency with investment management strategies, civil liberties, and privacy protection, are some of the important elements organizations consider when selecting appropriate courses of action. In those instances where organizations only identify a single course of action, then the evaluation is focused on whether the course of action is adequate. If the course of action is deemed inadequate, then organizations need to refine the identified course of action to address the inadequacies or develop another course of action (see Task 3-1)."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "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 Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations:\n\nnication and engagement with executive leadership. This team should leverage existing organizational expertise, like information security and compliance functions, when holistically assessing risk. 5.\nDo not wait to build deep supplier relationships : Direct points of contact and familiarity with a supplier's business are essential to understanding risks and ensuring rapid incident response. Strengthening such relationships can also foster loyalty, ensure effective supplier management, and support operational efficiencies. Organizations should also regularly stress test their Incident Response Plans and perform tabletop exercise simulations with their suppliers."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\nISCM, a critical step in an organization's Risk Management Framework (RMF), gives organizational officials access to security-related information on demand, enabling timely risk management decisions, including authorization decisions. Frequent updates to security plans, security assessment reports, plans of action and milestones, hardware and software inventories, and other system information are also supported. ISCM is most effective when automated mechanisms are employed where possible for data collection and reporting. Effectiveness is further enhanced when the output is formatted to provide information that is specific, measurable, actionable, relevant, and timely. While this document encourages the use of automation, it is recognized that many aspects of ISCM programs are not easily automated. The output of a strategically designed and well -managed organization-wide ISCM program can be used to maintain a system's authorization to operate and keep required system information and data (i.e., System Security Plan together with Risk Assessment Report, Security Assessment Report, and POA&M) up to date on an ongoing basis. Security management and reporting tools may provide functionality to automate updates to key evidence needed for ongoing authorization decisions. ISCM also facilitates risk-based decision making regarding the ongoing authorization to operate information systems and security authorization for common controls by provid ing evolving threat activity or vulnerability information on demand. A security control assessment and risk determination process, otherwise static between authorizations, is thus transformed into a dynamic process that supports timely risk response actions and cost-effective, ongoing authorizations. Continuous monitoring of threats, vulnerabilities, and security control effectiveness provides situational awareness for risk-based support of ongoing authorization decisions."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\n3.2.2 | Resource Access Control | 3-10 |\n| | | 3. 3.2.2. 3.2.2 Resource Access Control\n\nOnce the user has been granted access to the system as a whole, the question of which resources that authenticated user may access still remains."}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating 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 does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\n1 This document is currently under revision and will be reissued as Special Publication 800-30, Revision 1, Guide for Conducting Risk Assessments .\n\nThe provisional security impact level assignments contained in appendices C and D are only the first step in impact assignment and subsequent risk assessment processes. The impact assignments are not intended to be used by auditors as a definitive checklist for information types and impact assignments.\n\nThe level of impact on organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, or the Nation resulting from the operation of an information system given the potential impact of a threat and the likelihood of that threat occurring. [FIPS 200, Adapted]"}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "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 Guide to Integrating Forensic Techniques into Incident Response:\n\nes, cost, response time, and data sensitivity. - ! Incident handling teams should have robust forensic capabilities. More than one team member should be able to perform each typical forensic activity.\nHands-on exercises and IT and forensic training courses can be helpful in building and maintaining skills, as can demonstrations of new tools and technologies. - ! Many teams within an organization should participate in forensics. Individuals performing forensic actions should be able to reach out to other teams and individuals within an organization, as needed, for additional assistance. Examples of teams that may provide assistance in these efforts include IT professionals, management, legal advisors, human resources personnel, auditors, and physical security staff. Members of these teams should understand their roles and"}], "metadata": {"source": "Guide to Integrating Forensic Techniques into Incident Response", "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 Zero Trust Architecture provide? (Part 3)"}, {"role": "assistant", "content": "ores disponibles para el propósito. En esta publicación puede haber referencias a otras que actualmente están siendo desarrolladas por NIST de acuerdo con sus responsabilidades estatutarias asignadas.\nLa información contenida en esta publicación, incluidos conceptos y metodologías, puede ser utilizada por los organismos federales incluso antes de la finalización de dichas publicaciones complementarias. Por lo tanto, hasta que se finalice cada publicación, los requisitos, directrices y procedimientos actuales, cuando existan, seguirán siendo operativos. A efectos de planificación y transición, los organismos federales pueden seguir de cerca el desarrollo de estas nuevas publicaciones del NIST. Se anima a las organizaciones a revisar todos los borradores de publicaciones durante los periodos de comentarios públicos y proporcionar retroalimentación al NIST. Muchas publicaciones sobre ciberseguridad del NIST, aparte de las mencionadas anteriormente, están disponibles en https://csrc.nist.gov/publications. ## Los comentarios sobre esta publicación pueden enviarse a\n\nInstituto Nacional de Estándares y Tecnología A la atención de: Advanced Network Technologies Division, Information Technology Laboratory\n\n100 Bureau Drive (Mail Stop 8920) Gaithersburg, MD 20899-8920\n\nCorreo electrónico: zerotrust-arch@nist.gov\n\nTodos los comentarios están sujetos a la Ley de Libertad de Información (FOIA). ## Informes sobre tecnología de sistemas informáticos\n\nEl Laboratorio de Tecnología de la Información (ITL, por su nombre en inglés, Information Technology Laboratory) del Instituto Nacional de Estándares y Tecnología (NIST) promueve la economía y el bienestar público de Estados Unidos a través de su liderazgo técnico en la infraestructura de medición y normalización del país."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide for Conducting Risk Assessments provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-30 Revision 1\n\n\n\n## Guide for Conducting Risk Assessments\n\nJOINT TASK FORCE TRANSFORMATION INITIATIVE\n\n## I N F O R M A T I O N S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nSeptember 2012\n\n\n\n## U.S. Department of Commerce\n\nRebecca M. Blank, Acting Secretary\n\n## National Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary for Standards and Technology and Director\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\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."}], "metadata": {"source": "Guide for Conducting Risk Assessments", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Standard Security Label for GOSIP_ an Invitational Workshop:\n\nThe paper presents several alternative strategies for a building a Multipolicy Machine. It explores the critical metapolicy concept and raises issues about technical feasibility, control, NCSC acceptance, evaluation and export\n\nThe Trusted Computer System Evaluation Criteria (TCSEC or Orange Book) defines the United States' security paradigm. It assumes a single 'system security policy' which is divided into three major subpolicies: Confidentiality, Integrity, and Assurance of Service. The subpolicies are further subdivided. Confidentiality is divided into Access Control and Non-Access Control policies. Access Control policies are subdivided into Mandatory Access Control (MAC) and Discretionary Access Control (DAC). However, the paradigm assumes that all these subpolicies cohere together to represent one overall system security policy. The single overall policy drives the choice of security mechanisms and is the foundation of most assurance efforts.\n\nHandle bottom-up system construction. The end-user, supposedly the originator of the system security policy, can't change the security policy already implemented without reevaluation. The end-user must purchase components with security policies that come close to his needs, but a perfect match is unlikely. We need a paradigm which permits the end-user to establish his own security policy in a near-match system without requiring a reevaluation of the whole system."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh:\n\n- Multiple, loosely coupled microservices communicate through network calls, and these communication links must be protected. In the case of monolithic applications, these communications take place through procedure calls.\n- The entire network and all microservices are untrusted. Therefore, mutual authentication and secure communication channels between microservices through mechanisms such as mutual Transport Layer Security (TLS) (mTLS) are required.\n- The logging data that pertains to each microservice must be consolidated to obtain a security profile in order for forensics, audits, and analytics to assess the overall health of the application.\n\nMicroservices-based applications require several application infrastructure and security services, such as authentication, authorization, monitoring, logging, auditing, traffic control, caching, secure ingress, service-to-service, and egress communication. The reference hosting platform with interfaces for efficiently scheduling and running the multiple services of an application lacks the interfaces to run a set of application infrastructure services in a coordinated and consistent manner. Moreover, the following advantages of API architecture are not fully leveraged in the reference platform [8]:\n\nISMC-SR-1 : If certificate-based authentication is used for authenticating service calls, the signing certificate used by the service mesh's CA module should be rooted in the organization's existing Public Key Infrastructure (PKI) to allow for auditability, rotation, and revocation."}], "metadata": {"source": "Attribute-based Access Control for Microservices-based Applications using a Service Mesh", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Vulnerability Management:\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 authors-Kelley Dempsey and Eduardo Takamura of the National Institute of Standards and Technology (NIST), Paul Eavy of the Department of Homeland Security, and Dr. George Moore-wish to thank their colleagues who reviewed drafts and assisted in the production of this document, including Nathan Aileo, Ujwala Arikatla, Jim Foti, Ned Goren, John Groenveld, Frank Husson, Jaime Miller, Susan Pagan, Ron Ross, David Waltermire, Kimberly Watson, Isabel Van Wyk, Brett Kreider, Nate Lee, Jim Finegan, and Nolda Dooley."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Vulnerability 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 Guide to Protecting the Confidentiality of Personally Identifiable Information (PII):\n\nThe security objectives of integrity and availability are equally important for PII, and organizations should use the NIST Risk Management Framework 28 to determine the appropriate integrity and availability impact levels. Organizations may also need to consider PII-specific enhancements to the integrity or availability impact levels. Accuracy is a required Fair Information Practice for most PII, and the security objective of integrity helps to ensure accuracy. Integrity is also important for preventing harm to the individual and the organization. For example, unauthorized alterations of medical records could endanger individuals' lives, and medical mistakes based on inaccurate information can result in liability to the organization and harm to its reputation. Some PII does not need to have its confidentiality protected, such as information that the organization has permission or authority to release publicly (e.g., an organization publishing a phone directory of employees' names and work phone numbers so that members of the public can contact them directly). In this case, the PII confidentiality impact level would be not applicable and would not be used to supplement a system's provisional confidentiality impact level. PII that does not require confidentiality protection may still require other security controls to protect the integrity and the availability of the information, and the organization should provide appropriate security controls based on the assigned FIPS 199 impact levels. -The potential impact is LOW if the loss of confidentiality, integrity, or availability could be expected to have a limited adverse effect on organizational operations, organizational assets, or individuals."}], "metadata": {"source": "Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to An Introduction to Privacy Engineering and Risk Management in Federal Systems:\n\n| Executive Summary.............................................................................................. | Executive Summary.............................................................................................. | Executive Summary.............................................................................................."}], "metadata": {"source": "An Introduction to Privacy Engineering and Risk Management in Federal Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Applications Using Approved Hash Algorithms:\n\nAs described in Section 5.2, the overall security strength of a digital signature is limited by the collision resistance strength of the hash function. However, when using the randomized hashing technique specified in SP 800-106 [SP 800-106], a randomized hash function may support a higher level of security with respect to a particular potential vulnerability, offering enhanced protection to a message signer against a collision attack by a malicious message preparer who formulates the message to be signed, but does not actually sign the message."}], "metadata": {"source": "Recommendation for Applications Using Approved Hash Algorithms", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Approaches for Federal Agencies to Use the Cybersecurity Framework:\n\nybersecurity and other risks to be managed and facilitate communication among agency stakeholders, including executive leadership. 4 This use example aggregates elements of the activities of uses 2-8.\n| Summary: Using the Cybersecurity Framework's Functions (Identify, Protect, Detect, Respond, and Recover) as the basis for risk management dialogues related to the cybersecurity environment, organizations can raise awareness of cybersecurity and other risks to be managed and facilitate communication among agency stakeholders, including executive leadership. 4 This use example aggregates elements of the activities of uses 2-8. |\n| Typical Participants: Head of Agency (Chief Executive Officer), Risk Executive (Function), Chief Information Officer (CIO), Senior Information Security Officer/Chief Information Security Officer | Typical Participants: Head of Agency (Chief Executive Officer), Risk Executive (Function), Chief Information Officer (CIO), Senior Information Security Officer/Chief Information Security Officer |"}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "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 Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance:\n\nMr. Brady explained that OLIR applies set theory concepts for defining relationships as a mechanism to reduce subjectivity and retains the identity of the SME that defined each relationship. The program, defined in NISTIRs 8278 [NISTIR8278] and 8278A [NISTIR8278A], has a standardized process for submitting OLIRs to be added to the database. He noted that documentation of an IR in OLIR does not demonstrate certification or compliance to the NIST document in question.\n\nPersonal Identity Verification"}], "metadata": {"source": "Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\n\n## Interfaces for Personal Identity Verification\n\n## Interfaces for Personal Identity Verification\n\nFerraiolo H, Mehta K, Francomacaro S, Chandramouli R, Gupta S (2024) Interfaces for Personal Identity Verification: Part 3 - PIV Client Application Programming Interface. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-73pt3-5. https://doi.org/10.6028/NIST.SP.800-73pt3-5"}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "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 Communications Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\n| | Introduction .........................................................................................................................1 | Introduction .........................................................................................................................1 | |---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| | | Purpose.........................................................................................................................2 | | | | Scope............................................................................................................................2 | | | | Audience | .......................................................................................................................4 | | Intended Use........................................................................................................................5 | Intended Use........................................................................................................................5 | | | | EV/XFC Cybersecurity Mission Objectives.......................................................................5 | EV/XFC Cybersecurity Mission Objectives.......................................................................5 | | | Mission Objective 1: Deliver Reliable Performance through Secure Communications.6 | | | | Mission Objective 2: Maintain Resilience of the XFC Infrastructure..............................7 | | | | Mission Objective 3: Build and Maintain Trustworthy Relationships with Partners and Customers..............................................................................................................7 | | | | Mission Objective 4: Maintain Continuity of Operations................................................8 | | | | Overview of the Cybersecurity Framework ......................................................................8 | | | | The Framework Core ....................................................................................................9 | | | | Sector-Level Profiles | ...................................................................................................12 | | | XFC Baseline Profile .........................................................................................................12 | | | | Identify Function..........................................................................................................12 | | | 5.1.1."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "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 Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation:\n\n|\n| [Akamai] | J. Artega and W. Mejia, 'CLDAP Reflection DDoS,' Akamai Threat Advisory, April 2017.\nhttps://www.akamai.com/kr/ko/multimedia/documents/state-of-the- internet/cldap-threat-advisory.pdf |\n| [APNIC1] | G. Michaelson, 'MyAPNIC RPKI service now supports AS0 ROA creation,' APNIC technical note online, November 2018. https://blog.apnic.net/2018/11/09/myapnic-rpki-service-now-supports- as0-roa-creation/ |\n| [Arbor] | 'NETSCOUT Arbor's 13th Annual Worldwide Infrastructure Security Report' (2018). https://pages.arbornetworks.com/rs/082-KNA- 087/images/13th_Worldwide_Infrastructure_Security_Report.pdf |\n| [Arbor2] | 'NETSCOUT Arbor's 14th Annual Worldwide Infrastructure Security Report' (2019). https://www.netscout.com/sites/default/files/2019- 03/SECR_005_EN-1901%E2%80%93WISR.pdf |\n| [ARIN1] | 'Using RPKI at ARIN to certify resources,' ARIN online. https://www.arin.net/resources/rpki/using_rpki.html#hosted |\n| [ARIN2] | M."}], "metadata": {"source": "Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Metrics and Methodology for Hardware Security Constructs:\n\nory Ranges |\n| CWE-1240 | Use of a Cryptographic Primitive with a Risky Implementation |\n| CWE-1256 | Improper Restriction of Software Interfaces to Hardware Features |\n\n## 3.1.\nMeta Attack Patterns\n\n| ID | Description |\n|------|-----------------------------------------------------------------|\n| 167 | White Box Reverse Engineering |\n| 189 | Black Box Reverse Engineering |\n| 121 | Exploit Non-Production Interfaces |\n| 36 | Using Unpublished Interfaces or Functionality |\n| 1 | Accessing Functionality Not Properly Constrained by ACLs |\n| 180 | Exploiting Incorrectly Configured Access Control Security Level |\n| 68 | Subvert Code-signing Facilities |\n| 452 | Infected Hardware |\n| 456 | Infected Memory |\n| 97 | Cryptanalysis |\n| 625 | Mobile Device Fault Injection |"}], "metadata": {"source": "Metrics and Methodology for Hardware Security Constructs", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems.\n\nThe elements of an HSN may be independently owned, hosted, or virtualized by multiple organizations. While referring to Fig. 2, note that the operator may own the intellectual property that defines the virtualized payload control center (PCC) that is hosted on a third-party cloud service provider (CSP). The virtual PCC interfaces with a physical antenna field independent of the CSP, the operator, and the satellite antenna. All of this is transparent to the operators in organization A when they command, control, communicate or otherwise interact with payload A.\n\nHSN architectures may be complex and involve multiple stakeholders. As shown in Fig. 3, the physical and virtual architecture involves multiple independently owned satellites, uncrewed platforms, ground facilities and crosslinks supporting a range of independent HSNs. The organization that owns and operates the host (A) is operating two satellites that are supporting two independent HSNs (B and C). The operators associated with HSN B interface with a virtual payload command center that controls payloads on separate satellites. The crosslink and radio"}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "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 Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\n| Asset Management Category..................................................................................13 | |\n| 5.1.2. | Business Environment Category.............................................................................19 | |\n| 5.1.3. | Governance Category | .............................................................................................23 |\n| 5.1.4. | Risk Assessment Category .....................................................................................26 | |\n| 5.1.5. | Risk Management Category....................................................................................29 | |\n| 5.1.6."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\nRON ROSS VICTORIA PILLITTERI GARY GUISSANIE RYAN WAGNER RICHARD GRAUBART\n\nDEB BODEAU\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n\n\n## NIST Special Publication 800-172\n\n## Enhanced Security Requirements for Protecting Controlled Unclassified Information\n\nA Supplement to NIST Special Publication 800-171\n\n## RON ROSS VICTORIA PILLITTERI\n\nComputer Security Division\n\nNational Institute of Standards and Technology\n\n## GARY GUISSANIE RYAN WAGNER\n\nInstitute for Defense Analyses\n\nRICHARD GRAUBART DEB BODEAU\n\nThe MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-172\n\n## February 2021\n\n\n\nU.S. Department of Commerce Wynn Coggins, Acting Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\n## Periodic Reevaluation of the Program\n\nThe Director of Operations shall reevaluate and modify the Program from time to time as deemed appropriate. The Director of Operations shall base such reevaluation and modification on the following:\n\n1. Upon notification of a cybersecurity event, the Director of Operations must determine if the Incident Response Plan should be activated based on available information from event.\n2. The Director of Operations must inform all personnel listed in Section 3.5.7 of this document when the response plan has been activated.\n3. Impact to the manufacturing system must be determined by thorough investigation, and an incident type and severity level assigned. The Incident Report Template form should be used for this purpose. The severity level will be assigned by the Director of Operations in consultation with the IT Manager.\n4. Approval must be received from the CEO and General Counsel if additional resources (i.e., external entities) are to be contacted to assist with incident response (e.g., forensic investigators, IT consultants, cybersecurity consultants, law enforcement, etc.).\n5. The Director of Operations or IT Manager must coordinate the Incident Response Plan with stakeholders.\n6. User awareness, training, and testing procedures must be reviewed after every incident and updated as necessary.\n7. The General Counsel should be involved throughout the incident response due to the potential for legal action arising from the incident."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\n3.4.1 | Versions of SSL and TLS... 3.4.1 through 3. 3.4.1 Versions of SSL and TLS\n\nIn this document, the terms SSL and TLS are often used together to describe the same protocol."}], "metadata": {"source": "Guide to SSL VPNs", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 5)"}, {"role": "assistant", "content": "................................................................................. 1\n\nSymbols and abbreviated terms......................................................................................\n1\n\nDocument organization .................................................................................................... 1\n\nGeneral....................................................................................................................... 1\n\nModification ................................................................................................................ 2\n\nCMVP-approved security function requirements ........................................................... 2\n\nPurpose ...................................................................................................................... 2\n\nApproved security functions ........................................................................................ 2\n\nAppendix A. Document Revisions ....................................................................................... 3\n\n## Scope\n\nThis document specifies the Cryptographic Module Validation Program (CMVP)-approved security functions and supersedes those specified in International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 19790 Annex C and ISO/IEC 24759 paragraph 6.15. This document also supersedes SP 800-140Cr1. ## Normative references\n\nThis section identifies the normative references cited as ISO/IEC 19790 and ISO/IEC 24759. The specific editions to be used are ISO/IEC 19790:2012 and ISO/IEC 24759:2017. Please note that the version 19790:2012 referenced here includes the corrections made in 2015. National Institute of Standards and Technology (2019) Security Requirements for Cryptographic Modules . (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 140-3."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Guide to Attribute Based Access Control (ABAC) Definition and Considerations:\n\n3.3.2 | 3. 3.3.2 Attribute Source Minimization\n\nMinimizing the number of attribute sources used in authorization decisions may improve performance and simplify the overall security management of the ABAC solution."}], "metadata": {"source": "Guide to Attribute Based Access Control (ABAC) Definition and Considerations", "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 Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI provide? (Part 4)"}, {"role": "assistant", "content": "1-2\n\n1-2\n\n1-2\n\n1-2\n\n1-3\n\n2-1\n\n2-1\n\n2-1\n\n2-2\n\n2-2\n\n2-3\n\n2-3\n\n2-3\n\n2-3\n\n2-4\n\n2-4\n\n3-1\n\n3-1\n\n3-1\n\n3-1\n\n3-2\n\n3-2\n\n3-2\n\n3-2\n\n4-1\n\n4-1\n\n4-1\n\n4-1\n\n4-2\n\n4-2\n\n4-3\n\n4-3\n\n4-3\n\n4-4\n\n5-1\n\n5-1\n\n5-1\n\n5-1\n\n5-1\n\n\f6.\nCOMPUTER SECURITY\n\n6.1\n\n6.2\n\n6.3\n\n6.4\n\n6.5\n\nCryptographic Standards\nData Encryption Validation Tests\nMessage Authentication Code (MAC) Validation System\nKey Management Validation System (KMVS) . General\n\n6.5.1\n\n6.5.2\n\n6.5.3\n\nRequest for Validation\n\nInformation about Validated Products\nValidation Documentation\n\n. 7. PRODUCT DATA CONFORMANCE TESTING\n\n7.1\n\n7.1.1\n\n7.1.2\n\nIGES\n\nCertification\nIGES Validated Products\n\n. ,\n\n8. OSI PRODUCTS DATABASE\n\nAPPENDIX A FIPS CONFORMANCE TESTING PRODUCTS AND SERVICES\n\n6-1\n\n6-1\n\n6-1\n\n6-1\n\n6-1\n\n6-2\n\n6-2\n\n6-2\n\n6-2\n\n7-1\n\n7-1\n\n7-1\n\n8-1\n\nA-l\n\n\f1\n\n1. INTRODUCTION\n\n1.1\n\nPurpose\n\nThe testing of Information Technology (IT) Products to determine the degree to which they conform to\nspecific Federal Information Processing Standards (FIPS) may be required by Government agencies as\nspecified by the FIPS, Federal Information Resources Management Regulation (FIRMR) Parts 201-\n20.303, 201-20.304, and 201-39.1002, and the associated Federal ADP and Telecommunications\nProducts having a current validation certificate or test report may be offered or\nStandards Index. delivered by vendors in response to requirements as set forth in solicitations by Federal agencies. The\nValidated Products List (VPL) contains conformance testing information for the following IT Standards:\n\nProgramming Languages COBOL, Fortran, Ada, Pascal, C, and M[UMPS]\nDatabase Language SQL\nGraphics\nPOSIX\nComputer Security\nOpen Systems Interconnection (OSI)\nProduct Data (IGES)\n\nThis List is updated and published quarterly. The information contained herein is supplied by the\ncontributors listed in Section 2.6 and Appendix A, and is current as of the tenth of the month preceding\nthe publication date. Copies of the VPL may be obtained from:\n\nNational Technical Information Service\nU.S."}], "metadata": {"source": "Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\nChief Information Officer (CIO). The CIO leads the organization's ISCM program. The CIO ensures that an effective ISCM program is established and implemented for the organization by establishing expectations and requirements for the organization's ISCM program; working closely with authorizing officials to provide funding, personnel, and other resources to support ISCM; and maintaining high-level communications and working group relationships among organizational entities. | Malware [NISTIR 7298] | A program that is inserted into a system, usually covertly, with the intent of compromising the confidentiality, integrity, or availability of the victim's data, applications, or operating system or of otherwise annoying or disrupting the victim."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal 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 Access Control?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\n| APPENDIX B GLOSSARY.............................................................................................. | B-1 |\n| APPENDIX C ACRONYMS ............................................................................................. | APPENDIX C ACRONYMS ............................................................................................. | C-1 |\n| APPENDIX D TECHNOLOGIES FOR ENABLING ISCM......................................................... | APPENDIX D TECHNOLOGIES FOR ENABLING ISCM......................................................... | D-1 |"}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Security Assessment?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop:\n\nManufacturer support comprises a number of activities, especially documentation and software updates. An on-going challenge for customers and users in assessing and improving IoT device cybersecurity is inadequate documentation of device characteristics. Lack of documentation hinders both security assessments and the ability to select compensating security controls to address IoT device cybersecurity shortcomings. While some manufacturers do provide substantive documentation, many provide very little, leaving customer organizations starved for information on which to base risk assessments. Both the development of security solutions and the assessment of those solutions require information about, for example, the network communications patterns expected for IoT devices. Manufacturer communications regarding IoT device cybersecurity need to address a range of audiences with diverse levels of sophistication and understanding of the cybersecurity challenge. This includes communication both at the consumer level and with organizational procurement activities. Vendors need to convey information about product operation and about using device cybersecurity features, as well as more general communications regarding manufacturer procedures and commitments for vulnerability disclosure, software update frequency and mechanisms, and duration of support commitments for IoT products. Derail Heiland explained 'we need to be able to get detailed information around those specific security topics on how do we reduce risk by properly implementing. How do we deploy into our organization? How do we get the detailed information to help us make those security risks evaluations for better deploying the technology? Often we are not seeing that information.'\n\nThe introduction of IoT devices creates significant challenges for security assessment of federal information systems."}], "metadata": {"source": "Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for Evaluating Differential Privacy Guarantees:\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 800series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Unfortunately, de-identifying data is challenging in practice because it is difficult to distinguish identifying information from non-identifying information. Every person has a unique combination of features. Any one feature (e.g., gender or age) my not be uniquely identifying on its own, but as features accumulate they inevitably become uniquely identifying in combination. As a result, de-identified data nearly always contains some information that could be identifying."}], "metadata": {"source": "Guidelines for Evaluating Differential Privacy Guarantees", "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": "How does IoT Device Cybersecurity Capability Core Baseline support CMMC certification?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nEmail: iotsecurity@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nDevice cybersecurity capabilities are cybersecurity features or functions that computing devices provide through their own technical means (i.e., device hardware and software). This publication defines an Internet of Things (IoT) device cybersecurity capability core baseline, which is a set of device capabilities generally needed to support common cybersecurity controls that protect an organization's devices as well as device data, systems, and ecosystems."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to LTE Security:\n\n| Purpose and Scope ........................................................................................\n| 6 |\n| | 1.2 | Document Structure........................................................................................ | 6 |\n| | 1.3 | Document Conventions..................................................................................."}], "metadata": {"source": "Guide to LTE Security", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Guidelines for API Protection for Cloud-Native Systems:\n\n3.2.1. 3.2.1."}], "metadata": {"source": "Guidelines for API Protection for Cloud-Native Systems", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Random Bit Generator (RBG) Constructions:\n\nStandards and Technology (2019) Security Requirements for Cryptographic Modules. (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 140-3.\nhttps://doi.org/10.6028/NIST.FIPS.140-3 |\n| [FIPS_140IG] | National Institute of Standards and Technology, Canadian Centre for Cyber Securit y (2020) Implementation Guidance for FIPS 140-3 and the Cryptographic Module Validation Program, [Amended April 18, 2025]. |\n| [FIPS_180] | National Institute of Standards and Technology (2015) Secure Hash Standard (SHS). (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 180-4. |\n| [FIPS_197] | https://doi.org/10.6028/NIST.FIPS.180-4 National Institute of Standards and Technology (2001) Advanced Encryption Standard (AES). (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 197- |\n| [FIPS_202] | National Institute of Standards and Technology (2015) SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions. (Department of Commerce, Washington, DC), Federal Information Processing |\n| [ISO_18031] | https://doi.org/10.6028/NIST.FIPS.202 International Organization for Standardization/International Electrotechnical Commission (2025) ISO/IEC 18031:2025 Information technology -Security techniques-Randombitgeneration (International Organization for Standardization, Geneva, Switzerland). Available at |\n| [NISTIR_8427] | https://www.iso.org/standard/81645.html Buller D, Kaufer A, Roginsky AL, Sonmez Turan M(2022) Discussion on the Full Entropy Assumption of SP 800-90 Series."}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.6 (NIST 3.3.6)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case:\n\n3.3.6. 3.3.6. 3.3.6."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "nist_control": "3.3.6", "cmmc_practice_id": "AU.L2-3.3.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The NIST Definition of Cloud Computing provide? (Part 3)"}, {"role": "assistant", "content": "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, though attribution is desired. Nothing in this document should be taken to contradict standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority, nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official. ## 1.2 Purpose and Scope\n\nCloud computing is an evolving paradigm. The NIST definition characterizes important aspects of cloud computing and is intended to serve as a means for broad comparisons of cloud services and deployment strategies, and to provide a baseline for discussion from what is cloud computing to how to best use cloud computing. The service and deployment models defined form a simple taxonomy that is not intended to prescribe or constrain any particular method of deployment, service delivery, or business operation. ## 1.3 Audience\n\nThe intended audience of this document is system planners, program managers, technologists, and others adopting cloud computing as consumers or providers of cloud services. ## 2."}], "metadata": {"source": "The NIST Definition of Cloud Computing", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\n| Executive Summary......................................................................................................v | Executive Summary......................................................................................................v | Executive Summary......................................................................................................v |\n|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | Introduction ............................................................................................................1 | |\n| | 1.1 Scope................................................................................................................"}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n3.4.2, 3."}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Usability and Security Considerations for Public Safety Mobile Authentication provide?"}, {"role": "assistant", "content": "## NISTIR 8080\n\n## Usability and Security Considerations for Public Safety Mobile Authentication\n\nYee-Yin Choong Joshua M. Franklin Kristen K. Greene\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8080\n\n\n\n## NISTIR 8080\n\n## Usability and Security Considerations for Public Safety Mobile Authentication\n\nYee-Yin Choong Kristen K. Greene Information Access Division Information Technology Laboratory\n\nJoshua M. Franklin Applied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8080\n\nJuly 2016\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director\n\n## National Institute of Standards and Technology Interagency Report 8080 3 9 pages (July 2016)\n\n## This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8080\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": "Usability and Security Considerations for Public Safety Mobile Authentication", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\n800-39. https://doi.org/10.6028/NIST.SP.800-39\n- [7] Joint Task Force (2018) Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-37 Rev. 2. https://doi.org/10.6028/NIST.SP.800-37r2\n- [8] Grassi PA, Garcia ME, Fenton JL (2017) Digital Identity Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-63-3, Includes updates as of December 1, 2017. https://doi.org/10.6028/NIST.SP.800-63-3\n- [9] Office of Management and Budget (2017) Preparing for and Responding to a Breach of Personally Identifiable Information. (The White House, Washington, DC), OMB Memorandum M-17-12, January 3, 2017. Available at https://www.whitehouse.gov/sites/whitehouse.gov/files/omb/memoranda/2017/m-17-12\\_0.pdf\n- [10] Joint Task Force Transformation Initiative (2013) Security and Privacy Controls for Federal Information Systems and Organizations. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-53, Rev. 4, Includes updates as of January 22, 2015. https://doi.org/10.6028/NIST.SP.800-53r4\n- [11] Grassi PA, Lefkovitz NB, Nadeau EM, Galluzzo RJ, Dinh AT (2018) Attribute Metadata: A Proposed Schema for Evaluating Federated Attributes. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) 8112. https://doi.org/10.6028/NIST.IR.8112"}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "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.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 does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\ncurity officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\nAs we push computers to 'the edge,' building a complex world of interconnected information systems and devices, security and privacy risks (including supply chain risks) continue to be a large part of the national conversation and topics of great importance. The significant increase in the complexity of the hardware, software, firmware, and systems within the public and private sectors (including the U.S. critical infrastructure) represents a significant increase in attack surface that can be exploited by adversaries. Moreover, adversaries are using the supply chain as an attack vector and effective means of penetrating our systems, compromising the integrity of system elements, and gaining access to critical assets."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to Guidelines on Active Content and Mobile Code:\n\n3.1.6 Configuration of Software\n\nUnderstanding a system's security posture and correctly setting its configuration is an unrealistic expectation for the general population."}], "metadata": {"source": "Guidelines on Active Content and Mobile Code", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Standard Security Label for GOSIP_ an Invitational Workshop provide? (Part 5)"}, {"role": "assistant", "content": "| , \"Security Labels at the Transport Layer\" (Presentation Slides) , Wayne A.\nJansen (NIST) - | 95 |\n| Comments on the draft FIPS \"Standard Security Label for the Government Open Systems Interconnection Profile\" (Position Paper) , Russell Housley, Sammy Migues (Xerox Special Information Systems) \"The Multipolicy Machine - A New Paradigm for Multilevel Security Systems\" (Position Paper) , Hilary Hosmer (Data Security, Inc.) | Comments on the draft FIPS \"Standard Security Label for the Government Open Systems Interconnection Profile\" (Position Paper) , Russell Housley, Sammy Migues (Xerox Special Information Systems) \"The Multipolicy Machine - A New Paradigm for Multilevel Security Systems\" (Position Paper) , Hilary Hosmer (Data Security, Inc.) | 105 |\n| \"Modelling Security Policy and Labelling Unclassified but Sensitive Information - A Canadian (Position Paper) , D.S. Crawford (Canadian Department National | \"Modelling Security Policy and Labelling Unclassified but Sensitive Information - A Canadian (Position Paper) , D.S."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 ISCMA_ An Information Security Continuous Monitoring Program Assessment 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\n\nEmail: sec-cert@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\nThis publication describes an example methodology for assessing an organization's Information Security Continuous Monitoring (ISCM) program. It was developed directly from NIST guidance and is applicable to any organization, public or private. It can be used as documented or as the starting point for a different methodology. Included with the methodology is a reference implementation that is directly usable for conducting an ISCM assessment. ## Keywords\n\nassessment; continuous monitoring; information security continuous monitoring; information security continuous monitoring assessment; ISCM; ISCMA; ISCMAx."}], "metadata": {"source": "ISCMA_ An Information Security Continuous Monitoring Program Assessment", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Maintenance?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8572/final, including related content, potential updates, and document history.\n\nThis report summarizes discussions held at the March 5, 2025 \"Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' organized by the NIST Cybersecurity for the Internet of Things (IoT) program. This workshop follows an earlier event held in December 2024 titled 'Workshop on Updating Manufacturer Guidance for Securable Connected Product Development' to identify major update areas to NIST IR 8259. Similarly, the purpose of this more recent workshop was to discuss planned updates to NIST IR 8259 and gather additional feedback on taking a product viewpoint with greater emphasis on the IoT product lifecycle, expanded discussion of risk analysis, application to industrial contexts, and cybersecurity considerations around data management to support privacy goals. Over time, NIST work has built upon the concepts introduced in the NIST IR 8259, as reflected in subsequent publications that elaborate on IoT cybersecurity for specific sectors and use cases (e.g., federal agency use of IoT, consumer use of IoT in the home or in small businesses).\n\nOn March 5, 2025, NIST's Cybersecurity for Internet of Things (IoT) program hosted 'Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' to continue discussion of potential updates to Foundational Cybersecurity Activities for IoT Device Manufacturers, NIST IR 8259 [1]. The March workshop follows the December 4 th , 2024, workshop titled 'Workshop on Updating Manufacturer Guidance for Securable Connected Product Development' which first explored potential updates to NIST IR 8259."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to Foundational Cybersecurity Activities for IoT Device Manufacturers:\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. Manufacturers are creating an incredible variety and volume of internet-ready devices broadly known as the Internet of Things (IoT). Many of these IoT devices do not fit the standard definitions of information technology (IT) devices that have been used as the basis for defining device cybersecurity capabilities (e.g., smartphones, servers, laptops). The IoT devices in scope for this publication have at least one transducer (sensor or actuator) for interacting directly with the physical world and at least one network interface (e.g., Ethernet, Wi-Fi, Bluetooth, LongTerm Evolution [LTE], Zigbee, Ultra-Wideband [UWB]) for interfacing with the digital world. The IoT devices in scope for this publication can function on their own, although they may be dependent on specific other devices (e.g., an IoT hub) or systems (e.g., a cloud) for some functionality. Many IoT devices have computing functionality, data storage, and network connectivity along with functionality associated with equipment that previously lacked these computing functions (e.g., smart appliances). In turn, these functions enable new efficiencies and technological capabilities for the equipment, such as remote access for monitoring, configuration, and troubleshooting."}], "metadata": {"source": "Foundational Cybersecurity Activities for IoT Device Manufacturers", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n3.3.3. 3.3.3. 3.3.3), the upstream IdP may not be able to generate a PPI for the downstream RP, since the proxy could blind the IdP from knowing which RP is being accessed by the subscriber."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\nincludes the process of working with a help desk to provide assistance for end users. 5. Manage the Solution. After the SSL VPN solution has been deployed, it must be managed throughout its lifecycle.\nManagement includes maintenance (e.g., patching, solution expansion, key management, policy changes), performance monitoring, and periodic testing/validation of the solution. The handling of operational issues must also be considered."}], "metadata": {"source": "Guide to SSL VPNs", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio:\n\nMilestones (POA&M) document. A private-sector organization determines that a risk will require funding from next fiscal year to fully address and records the corresponding risk plan in a project plan.\n|\n| | MA.RR-6 : Risk analysis is revised after risk responses are determined to reflect the envisioned reduction of likelihood and impact from each risk response. | An organization updates the Current Assessment - Likelihood, Impact, and Exposure Rating fields of a risk register after the risk responses have been documented. |\n| | MA.RR-7: Controls are implemented or adjusted to perform risk response plans. | An organization implements security controls to enact a risk response, and those actions are recorded in the Risk Response Description field of a risk register. |\n| | MA.RR-8 : Residual risk is forecasted for each risk after risk responses are decided. | An organization estimates its residual risk and records it in the Residual Risk field of a risk register. |\n| Risk Monitoring, Evaluation, and Adjustment (MA.RM): Risks are checked and assessed, and risk responses are adapted as needed. | MA.RM-1 : Risk conditions are continually monitored against risk tolerance to ensure conditions remain within acceptable levels. | Risks are measured and benchmarked according to key performance indicators (KPIs) and key risk indicators (KRIs), respectively. |\n| Risk Monitoring, Evaluation, and Adjustment (MA.RM): Risks are checked and assessed, and risk responses are adapted as needed."}], "metadata": {"source": "Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio", "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 Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies:\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\ncombination of user behavioral and physical data. Also, virtual environments require significant amounts of data and similarly significant technological protections for data (e.g., encryption, local or on-device processing). This can present costs and trade-offs (e.g., privacy and security vs. safety).\n\nSpecific to privacy, the following key considerations for immersive technologies were highlighted through discussions. Participants noted that there could be tensions between data minimization requirements and the amount and variety of data needed to power immersive technologies. Also, principles such as consent, user control, and autonomy may be difficult to uphold for involuntary and unconscious or subconscious behaviors or physical acts."}], "metadata": {"source": "Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies", "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 Automation Support for Security Control Assessments_ Volume 1_ Overview:\n\ntion of Volume 1.......................................................................................................3 |\n| 2.\nOverview of an Automated Security Control Assessment Process .......................................4 |\n| 2.1 Prerequisites to Automated Security Control Assessment......................................................4 |\n| 2.2 Automating the Test Assessment Method................................................................................5 |\n| 2.2.1 Terms for Referring to Assessment Objects......................................................................6 |\n| 2.3 Factors for Determining When to Trust Automated Ongoing Assessments ...........................6 |\n| 2.4 An Automated Security Control Assessment Program: ISCM................................................7 |\n| 2.5 Preparing for Automated Security Control Assessments........................................................9 |\n| 3."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "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 Computer Security Division 2008 Annual Report:\n\nDuring FY2008 CSD explored opportunities to apply its security research to national priorities and internal NIST initiatives. The CSD has played an active role in implementation planning for the Comprehensive National Cyber Security Initiative to protect our country's critical infrastructure. The CSD continued to expand its support for two key national initiatives, electronic voting and health information technology, by researching the security requirements of those areas and applying the results of that research, along with current technologies, to advance the stated goals of those initiatives. CSD also worked closely with the ITL management team to integrate security projects into ITL's research programs. These programs, which include Cyber Security, Pervasive Information Technologies, Identity Management, and Trustworthy Software, are designed to organize and build ITL core competencies in the most efficient manner, and to maximize the use of ITL resources to address emerging information technology challenges. This revision of SP 800-60 further clarifies the system security categorization process; discusses the impact of security categorization results on other enterprise-wide activities such as capital planning, enterprise architecture, and disaster recovery planning; and provides recommendations and rationale for mission-based and management and support information types. The requirement to measure information security performance is driven by regulatory, financial, and organizational reasons. A number of existing laws, rules, and regulations, such as the Clinger-Cohen Act, the Government Performance and Results Act (GPRA), and the Federal Information Security Management Act (FISMA), cite information performance measurement in general and information security measurement in particular as a requirement."}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to a Secure Enterprise Network Landscape:\n\n- Packet filters and network address translation: Packet filtering and Network address translation (NAT) are used to monitor and control packets moving across a network interface, apply predetermined security rules, and obscure the internal network from the public internet. - Stateful inspection: Stateful firewalling, also known as dynamic packet filtering, monitors the state of connections and makes determinations as to what types of data packets belong to a known active connection and can be allowed to pass through the firewall. - Deep packet inspection (DPI): This feature, also known as packet sniffing, examines the content of packets (both the header and the payload, unlike the stateful inspection that inspects only the packet header). In addition to the capability provided by stateful inspection, this has capabilities related to finding hidden threats within the data stream, such as attempts at data exfiltration, violations of content policies, malware, and more. - Threat detection and response: Modern firewalls can gather and analyze enough data across multiple packets and sessions to detect threats and security incidents targeted at a particular system or a family of systems. These data from multiple firewalls can also be directed toward security information and event management (SIEM) and correlated with data from other security tools and IT systems to detect enterprise-wide attacks that span multiple systems and network layers. In addition, these data can be used to understand evolving threats and define new access rules, attack patterns, and defensive strategies [6]. - Logging and auditing capabilities: Logging and auditing capabilities result in the construction of network events that can be used to identify patterns of performance and security issues. - Access control functions: Access control functions enforce granular sophisticated access control policies."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\n| Category | Subcategory and Selected Informative References | Ransomware Application | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Identify | | | | Asset Management (ID.AM): The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to organizational objectives and the organization's risk strategy."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Foundations of a Security Policy for Use of the National Research and Educational Network:\n\nThe National Research and Education Network is one part of a Federal program establishing a comprehensive set of computing and communications services throughout the nation's scientific and educational communities. It consists of a large number of Federal, State and commercial entities providing and using a wide range of services. As such, it will be organized as a cooperative with a membership including service suppliers and users with a distributed management structure. Basic security services will be expected by most users with special security services required by others."}], "metadata": {"source": "Foundations of a Security Policy for Use of the National Research and Educational Network", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\n| Subcategory | Applicability to HSNs | Informative References |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| PR.IP-1: A baseline configuration of information technology/industrial control systems is created, maintained, and incorporates security principles (e.g., concept of least functionality). | Focus on the configuration and maintenance of the entities at the interface to the HSN. Baseline and configuration are internal concerns, and obtaining detailed configuration information from the partners is not practical. | NIST SP 800-53 Rev. 5 CM-1, CM-2, CM-3, CM-4, CM-5, CM-6, CM-7, CM-9, SA-10 NIST SP 800-137 Section D NIST SP 800-160V1 3.4.9, 3.4.10, 3.4.11, Appendix F, Appendix G |\n| PR.IP-2: ASystem Development Life Cycle (SDLC) to manage systems is implemented."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "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 Security Assessment?"}, {"role": "assistant", "content": "According to 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\nAgent i on also should fully document in-place controls to ease | >< * i iodic reevaluation, internal audit, and oversight agency rev i ew | | | | | | | | | | | PAGE | | | | | | | | | | | |-----------------------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|--------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------|------------------------------------------| | ABSTRACT | | | | | | | | | | iii | | | | | | | | | | | | LETTER | FROM | JAMES H."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "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.7 (NIST 3.1.7)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.1.7."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "nist_control": "3.1.7", "cmmc_practice_id": "AC.L2-3.1.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Cryptographic Algorithms and Key Sizes for Personal Identity Verification:\n\n3.2.3. 3.2.3. 3.2.3."}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\nCSF Tiers | Function | Category | Category Identifier | |---------------|---------------------------------------------------------|-----------------------| | Govern (GV) | Organizational Context | GV.OC | | Govern (GV) | Risk Management Strategy | GV.RM | | Govern (GV) | Roles, Responsibilities, and Authorities | GV.RR | | Govern (GV) | Policy | GV.PO | | Govern (GV) | Oversight | GV.OV | | Govern (GV) | Cybersecurity Supply Chain Risk Management | GV.SC | | Identify (ID) | Asset Management | ID.AM | | Identify (ID) | Risk Assessment | ID.RA | | Identify (ID) | Improvement | ID.IM | | Protect (PR) | Identity Management, Authentication, and Access Control | PR.AA | | Protect (PR) | Awareness and Training | PR.AT | | Protect (PR) | Data Security | PR.DS | | Protect (PR) | Platform Security | PR.PS | | Protect (PR) | Technology Infrastructure Resilience | PR.IR | | Detect (DE) | Continuous Monitoring | DE.CM | | Detect (DE) | Adverse Event Analysis | DE.AE | | Respond (RS) | Incident Management | RS.MA | | Respond (RS) | Incident Analysis | RS.AN | | Respond (RS) | Incident Response Reporting and Communication | RS.CO | | Respond (RS) | Incident"}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "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 Guidelines on Firewalls and Firewall Policy:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guidelines on Firewalls and Firewall Policy", "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 PIV Card to Reader Interoperability Guidelines provide? (Part 5)"}, {"role": "assistant", "content": "3 | PIV Contact Card Reader (Physical Access).............................................................. 3 |\n| | 2.2.1 | Common Requirements ..................................................................................3 |\n| 2.3 | PIV Contactless Card Reader (Logical Access).......................................................... 3 | PIV Contactless Card Reader (Logical Access).........................................................."}], "metadata": {"source": "PIV Card to Reader Interoperability Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Using Business Impact Analysis to Inform Risk Prioritization and Response:\n\nts and stores the results in the BIA Register. An asset criticality or resource dependency assessment identifies and prioritizes the information assets that support the enterprise's critical missions.\nSimilarly, assessments of asset sensitivity identify and prioritize information assets that store, process, or transmit information that must not be modified or disclosed to unauthorized parties. In the cybersecurity realm, the use of the BIA has historically been limited to calculations of quality-based and time-based objectives for incident handling (including continuity of operations and disaster recovery). Because the BIA serves as a nexus for understanding risk (which is the measurement of uncertainty on the mission), it provides a basis for risk appetite and tolerance values as part of the enterprise risk strategy. 1 That guidance supports performance and risk metrics based on the relative value of enterprise assets to communicate and monitor Cybersecurity Risk Management 2 (CSRM) activities, including measures determined to be key performance indicators (KPIs) and key risk indicators (KRIs). The BIA supports asset classification that drives requirements, risk communications, and monitoring. Expanding use of the BIA to include confidentiality and integrity considerations supports comprehensive risk analysis. The basis of asset valuation on enterprise impact helps to better align risk decisions to enterprise risk strategy. CSRM/ERM integration helps to complete the risk"}], "metadata": {"source": "Using Business Impact Analysis to Inform Risk Prioritization and Response", "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 Physical Protection?"}, {"role": "assistant", "content": "According to Fiscal Year 2022 Cybersecurity and Privacy Annual Report:\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": "Fiscal Year 2022 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Non-Fungible Token Security provide? (Part 2)"}, {"role": "assistant", "content": "aft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements\n\nNIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-02-02\n\n## How to Cite this NIST Technical Series Publication:\n\nMell P, Yaga D (2024) Non-Fungible Token Security. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8472. https://doi.org/10.6028/NIST.IR.8472\n\n## Author ORCID iDs\n\nPeter Mell: 0000-0003-2938-897X\n\nDylan Yaga: 0000-0003-4058-3645\n\n## Contact Information\n\nNISTIR8472@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8472/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nNon-fungible token (NFT) technology provides a mechanism to enable real assets (both virtual and physical) to be sold and exchanged on a blockchain. While NFTs are most often used for autographing digital assets (associating one's name with a digital object), they utilize a strong cryptographic foundation that may enable them to regularly support ownership-transferring sales of digital and physical objects. For this, NFT implementations need to address potential security concerns to reduce the risk to purchasers. This publication explains NFT technology and then identifies and discusses a list of 27 potential security issues."}], "metadata": {"source": "Non-Fungible Token Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to Security Segmentation in a Small Manufacturing Environment:\n\n\n\n## NIST Cybersecurity White Paper NIST CSWP 28\n\n## Security Segmentation in a Small Manufacturing Environment\n\nDr. Michael Powell National Cybersecurity Center of Excellence National Institute of Standards and Technology\n\nJohn Hoyt Aslam Sherule Dr. Lynette Wilcox The MITRE Corporation\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.CSWP.28\n\nApril 6 , 2023\n\n\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology (NIST), nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## 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 2023-03-3 0\n\n## How to Cite this NIST Technical Series Publication:\n\nPowell M, Hoyt J, Sherule A, Wilcox L (202 3 ) Security Segmentation in a Small Manufacturing Environment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 28. https://doi.org/10.6028/NIST.CSWP.28\n\n## Author ORCID iDs\n\nDr. Michael Powell: 0000-0002-3922-7435 John Hoyt: 0000-0002-0783-7036 Aslam Sherule: 0000-0002-2003-3817 Dr. Lynette Wilcox: 0000-0003-1246-6505\n\n## Contact Information\n\nmanufacturing\\_nccoe@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). ## Abstract\n\nManufacturers are increasingly targeted in cyber-attacks."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 3?"}, {"role": "assistant", "content": "According to Security Requirements for Cryptographic Modules:\n\n## FIPS PUB 140-3\n\n## FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION\n\n(Supersedes FIPS PUB 140-2)\n\n## SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES\n\nCATEGORY: INFORMATION SECURITY SUBCATEGORY: CRYPTOGRAPHY\n\nInformation Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8900\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.FIPS.140-3\n\nMarch 22, 2019\n\n\n\n## U.S. Department of Commerce\n\nWilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology\n\nWalter Copan, NIST Director and Under Secretary for Standards and Technology\n\n## FOREWORD\n\nThe Federal Information Processing Standards Publication Series of the National Institute of Standards and Technology (NIST) is the official series of publications relating to Standards and Guidelines adopted and promulgated under the provisions of the Federal Information Security Management Act (FISMA) of 2002. Comments concerning FIPS publications are welcomed and should be addressed to the Director, Information Technology Laboratory, National Institute of Standards and Technology, 100 Bureau Drive, Stop 8900, Gaithersburg, MD 20899-8900. Charles H. Romine, Director Information Technology Laboratory\n\n## Abstract\n\nThe selective application of technological and related procedural safeguards is an important responsibility of every federal organization in providing adequate security in its computer and telecommunication systems. This standard is applicable to all federal agencies that use cryptographic-based security systems to provide adequate information security for all agency operations and assets as defined in 15 U.S.C. § 278g-3. This standard shall be used in designing and implementing cryptographic modules that federal departments and agencies operate or are operated for them under contract."}], "metadata": {"source": "Security Requirements for Cryptographic Modules", "cmmc_level": "3", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Managing the Security of Information Exchanges:\n\n3.4.2 Emergency Discontinuance ... 3.4.2 Emergency Discontinuance\n\nIf a participating organization detects an attack, intrusion attempt, or other contingency that exploits or jeopardizes the information or systems involved in the information exchange, it might be necessary to abruptly terminate the information exchange without providing written notice to the other party."}], "metadata": {"source": "Managing the Security of Information Exchanges", "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 De-Identifying Government Datasets_ Techniques and Governance provide? (Part 5)"}, {"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 800series 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": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators:\n\nAssessing the SP 800-53controls of the system itself should ideally have a continual assessment component utilizing a monitoring program [13]. Frequent automated checks or scans should be conducted to detect changes in the system (as part of the MONITOR step below). Logging data should be used to detect possible malicious behavior that requires further investigations or remediation. This assessment may also include active processes such as red team testing of the system as input into the assessments."}], "metadata": {"source": "Planning for a Zero Trust Architecture_ A Planning Guide for Federal Administrators", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks:\n\naffecting such areas as configuration and patch management. - Differing lifespan expectations. A manufacturer may intend for a particular IoT device to only be used for a few years and then discarded.\nAn organization purchasing that device might want to use it for a longer time, but the manufacturer may stop supporting the device (e.g., releasing patches for known vulnerabilities) either by choice or because of supply chain limitations (e.g., supplier no longer releases patches for a particular IoT device component). The problem of differing lifespan expectations is not new and is not specific to IoT, but it may be particularly important for some IoT devices because of safety, reliability, and other risks potentially involved in using devices past their intended lifespan. - Unserviceable hardware. IoT device hardware may not be serviceable, meaning it cannot be repaired, customized, or inspected internally. - Lack of inventory capabilities. IoT devices brought into an organization may not be inventoried, registered, and otherwise provisioned via the normal IT processes. This is especially true for types of devices that did not previously have networking capabilities. - Heterogeneous ownership. There is often heterogeneous ownership of IoT devices. For example, an IoT device may transfer data to manufacturer-provided cloud-based service processing and storage. Data may also be sent to a cloud service to aggregate data from multiple IoT devices in a single location. These cloud services may have access to portions or all of the devices' data, or even access to and control of the devices themselves for monitoring, maintenance, and troubleshooting purposes. In some cases, only manufacturers have the authority to do maintenance; an organization attempting to install patches or do other maintenance tasks on an IoT device may void the warranty. Also, in IoT there may be little or no information available about device ownership,"}], "metadata": {"source": "Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Conformance Assessment of Transport Layer Security Implementations:\n\n- (1) Data Integrity,\n- (2) Data Confidentiality,\n- (3) Data Origination Authentication, and\n- (4) Access Control.\n\nEvaluations of commercial products in the U.S. are carried out through the Department of Defense (DoD) Trusted Product Evaluation Program (TPEP). The TPEP evaluates systems that meet the DoD's program objectives based on the criteria defined in the DoD TCSEC [7]. The TCSEC defines a hierarchy of classes that represent increasing levels of confidence in the trustworthiness of a computer system to protect information. The TCSEC identifies features to be evaluated, such as login, access controls, and audit; and assurances to be obtained, such as least privilege, testing, and documentation. Features are mechanisms that provide security functionality, while assurances indicate the degree of trust, and give a measure of the degree to which features work correctly and are effective."}], "metadata": {"source": "Conformance Assessment of Transport Layer Security Implementations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations.\n\nAll the components of telework and remote access solutions, including client devices, remote access servers, and internal resources accessed through remote access, should be secured against expected threats, as identified through threat models. Major security concerns include the lack of physical security controls, the use of unsecured networks, the connection of infected devices to internal networks, and the availability of internal resources to external hosts.\n\nOrganizations should ensure that all types of telework client devices are secured, including PCs, smartphones, and tablets. For PCs, this includes physical security. For devices other than PCs, security capabilities and the appropriate security actions vary widely by device type and specific products, so organizations should provide guidance to device administrators and users who are responsible for securing telework mobile devices on how they should secure them."}], "metadata": {"source": "Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide for Security-Focused Configuration Management of Information Systems:\n\n| system owner (or program manager) [SP 800-37] | An organizational official responsible for the procurement, development, integration, modification, operation, maintenance, and disposal of a system.\n|\n| system security officer [SP 800-37] | Individual with assigned responsibility for maintaining the appropriate operational security posture for an information system or program. |\n| system security plan | See information system security plan . |\n| system user [SP 800-37] | An individual or (system) process acting on behalf of an individual that is authorized to access information and information systems to perform assigned duties. Note: With respect to SecCM, an information system user is an individual who uses the information system functions, initiates change requests, and assists with functional testing. |\n| threat [SP 800-30] | Any circumstance or event with the potential to adversely impact organizational operations, organizational assets, individuals, other organizations, or the Nation through a system via unauthorized access, destruction, disclosure, modification of information, and/or denial of service. |\n| threat source [FIPS 200] | The intent and method targeted at the intentional exploitation of a vulnerability or a situation and method that may accidentally trigger a vulnerability. Synonymous with threat agent. |"}], "metadata": {"source": "Guide for Security-Focused Configuration Management of 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 guidance does Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4) provide?"}, {"role": "assistant", "content": "\n\n## Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4)\n\nWayne A. Jansen\n\nU.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Office of Weights and Measures Gaithersburg, MD 20899\n\n\n\nQC 100 . U56 49 34\n\n## Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocoi at Layer 4 (SP4)\n\n\n\nWayne A. Jansen\n\nU.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Office of Weights and Measures Gaithersburg, MD 20899\n\nOctober 1992\n\n\n\nU.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary\n\nTECHNOLOGY ADMINISTRATION Robert M. White, Under Secretary for Technology\n\nNATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director\n\n## TABLE OF CONTENTS\n\n| 1. | INTRODUCTION | INTRODUCTION | 1 |\n|-----------------------------------------------------------|-----------------------------------------------------------|-----------------------------------------------------------|-----|\n| | 1.1 | Background | 1 |\n| | 1.2 | Objectives | 1 |\n| 2. | INSTRUCTIONS | INSTRUCTIONS | 2 |\n| 3. | IDENTIFICATION | IDENTIFICATION | 3 |\n| 4."}], "metadata": {"source": "Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 CMVP Documentation Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nCMVP Validation Authority Updates to ISO/IEC 24759\n\nCMVP Validation Authority Updates to ISO/IEC 24759"}], "metadata": {"source": "CMVP Documentation Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - Can be used by organizations in any sector or community, regardless of size or cybersecurity sophistication\n- Can be applied to software developed to support information technology (IT), industrial control systems (ICS), cyber-physical systems (CPS), or the Internet of Things (IoT)\n- Can be integrated into any existing software development workflow and automated toolchain; should not negatively affect organizations that already have robust secure software development practices in place\n- Makes the practices broadly applicable, not specific to particular technologies, platforms, programming languages, SDLC models, development environments, operating environments, tools, etc."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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 Physical Protection?"}, {"role": "assistant", "content": "According to Recommended Cybersecurity Requirements for Consumer-Grade Router Products:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leade rship 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 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. - Machine-readable asset identification support. Consumer-grade routers serve as a central connection point for networks. Many types of devices will gain access to the local network and usually the internet. Consumer grade routers can be more proactive in managing the cybersecurity of the network when machine-readable asset identifiers are available. While home users could utilize machine-readable asset identification, it is more likely to be useful to small businesses or for routers leased from internet service providers (ISPs). Identification can also go beyond simple inventorying to include device type and firmware version, be extended by concepts like device intent signaling (e.g., the ' manufacturer usage description ' [MUD]) or be used more directly for the management of router devices ' firmware updates. Machine-readable asset identifiers must be developed and used in ways that are privacy preserving. - Interface and functionality minimization for consumer-grade router devices. ' Secureby-design ' principles [SecureByDesign] applied to consumer-grade routers should guide manufacturers to minimize the number of interfaces, both logical and physical and general functionality provided by the router device."}], "metadata": {"source": "Recommended Cybersecurity Requirements for Consumer-Grade Router Products", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Federal Information and Information Systems:\n\n1 An information system is a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. Information resources include information and related resources, such as personnel, equipment, funds, and information technology.\n\nThe minimum security requirements cover seventeen security-related areas with regard to protecting the confidentiality, integrity, and availability of federal information systems and the information processed, stored, and transmitted by those systems. The security-related areas include: (i) access control; (ii) awareness and training; (iii) audit and accountability; (iv) certification, accreditation, and security assessments; (v) configuration management; (vi) contingency planning; (vii) identification and authentication; (viii) incident response; (ix) maintenance; (x) media protection; (xi) physical and environmental protection; (xii) planning; (xiii) personnel security; (xiv) risk assessment; (xv) systems and services acquisition; (xvi) system and communications protection; and (xvii) system and information integrity. The seventeen areas represent a broad-based, balanced information security program that addresses the management, operational, and technical aspects of protecting federal information and information systems.\n\nAwareness and Training (AT): Organizations must: (i) ensure that managers and users of organizational information systems are made aware of the security risks associated with their activities and of the applicable laws, Executive Orders, directives, policies, standards, instructions, regulations, or procedures related to the security of organizational information systems; and (ii) ensure that organizational personnel are adequately trained to carry out their assigned information security-related duties and responsibilities."}], "metadata": {"source": "Minimum Security Requirements for Federal Information and Information Systems", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report", "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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n- Employing a botnet to send high volumes of connection requests to an internet-facing service, making it unavailable to legitimate service users\n- Obtaining administrative credentials at a software-as-a-service provider, which puts sensitive tenant data entrusted to that provider at risk\n- Intruding upon an organization's business network to steal credentials and use them to instruct industrial control systems to shut down or destroy critical physical components, causing a major service disruption\n- Deploying ransomware to prevent the use of computer systems and cause multiple data breaches by copying files from those systems\n- Using phishing emails to compromise user accounts and using those accounts to commit financial fraud\n- Identifying a new vulnerability in network management appliances and exploiting the vulnerability to gain unauthorized access to network communications\n- Compromising a vendor's software, which is subsequently distributed to customers in its compromised state\n\nProcesses and procedures should be based on the incident response policy and plan. Documented procedures should explain how technical processes and other operating procedures should be performed. Procedures can be tested or exercised periodically to verify their accuracy and can be used to help train new personnel. While it is impossible to have detailed procedures for every possible situation, organizations should consider documenting procedures for responding to the most common types of incidents and threats. Organizations should also develop and maintain procedures for particularly important processes that may be urgently needed during emergency situations, such as redeploying the organization's primary authentication platform."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\n| SECTION | SECTION | SECTION | PAGE |\n|-----------|--------------|-------------------------------------------------------------|--------|\n| | Abstract | | ii |\n| 1. | Introduction | Introduction | 1-1 |\n| | 1.1 | Background | 1-1 |\n| | | 1.1.1 Trusted Computer System ^valuation Criteria (TCSEC) | 1-2 |\n| | 1.1.2 | Information Technology Security Evaluation Criteria (TTSEC) | 1-2 |\n| | | 1.1.3 Security Requirements in the Commercial Sector | 1-3 |\n| | | 1.1.4 System Security Study Committee | 1-4 |\n| | | 1.1.5 Federal Criteria Project | 1-5 |\n| | | 1.1.6 Minimum Security Requirements | 1-5 |\n| | 1.2 | Scope of the MSR | 1-6 |\n| | 1.3 | Audience | 1-6 |\n| | 1.4 | Terminology | 1-7 |\n| | 1.5 | Document Organization | 1-7 |\n| 2."}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating 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 Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective provide? (Part 5)"}, {"role": "assistant", "content": "| Standards Developing Organizations (SDOs) ...........................................................................\n21 |\n| 7 | IT Standards Development .......................................................................................................30 |\n| 8 | Accelerating IT Standards Development .................................................................................. 34 |\n| 9 | Ongoing Issues in IT Standards Development .......................................................................... 36 |\n| 10 | How to Effectively Engage SDOs .......................................................................................... 38 |\n| Annex A - Terms and Definitions .................................................................................................... 41 | Annex A - Terms and Definitions .................................................................................................... 41 |\n| Annex B - Conformity Assessment ..................................................................................................."}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to 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 Personnel Security?"}, {"role": "assistant", "content": "According to Computer Security Division 2004 Annual Report:\n\nity CERT Coordination Center, the American Bankers Association, Ars Technica and EDUCAUSE. This area added twelve practices in the past year bringing the total number of listings to twenty.\nThe Defense Information Systems Agency (DISA) issues STIGs and checklists for a variety of information technologies and hosts these on its Web site. Many of these resources deal with classified system requirements, and hence access is restricted to military and government personnel only. Some of these resources, however, are suitable for non-classified system use. CSD, through an agreement with DISA, houses a repository of the STIGs and checklists that are suitable for non-classified systems so they may be accessed by contractors that handle Federal information systems. These guides and checklists are also available for voluntary adoption by others."}], "metadata": {"source": "Computer Security Division 2004 Annual Report", "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.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\n3.3.1. 3.3.1."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Computer Security Division 2013 Annual Report:\n\nivacy technologies, including privacy framework, privacy reference architecture, privacy infrastructure, anonymity and credentials, and specific privacyenhancing technologies\n\nGuidelines (VVSG) 1.1.\nThe security guidelines were updated in FY 2012 to improve the auditability of voting systems, to provide greater software integrity protections, to expand and improve access control requirements, and to help ensure cryptographic security mechanisms are implemented properly. In addition, CSD supported the efforts of the EAC and Federal Voting Assistance Program (FVAP) of DoD to improve the voting process for citizens under the Uniformed and Overseas Citizens Voting Act (UOCAVA) by leveraging electronic technologies. The team worked with the TDCG's UOCAVA Working Group to develop a risk analysis on technologies used in current UOCAVA voting processes, including vote-by-mail, online voter registration, electronic ballot delivery, and online ballot marking."}], "metadata": {"source": "Computer Security Division 2013 Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\n3.3.3 Mutual Authenticate with Derived PIV Token Management Key\n\n| Test Assertion | TA-08. 3.3.3 Public Key Size\n\n| Test Assertion | TA-09."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "nist_control": "3.3.3", "cmmc_practice_id": "AU.L2-3.3.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Introduction to Cybersecurity for Commercial Satellite Operations:\n\n| Informative SP 800-53, Rev. 4 | Reference SP 800-53, Rev.\n5 |\n|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|--------------------------------------------------|\n| | ID.SC-4: Suppliers and third- party partners are routinely assessed using audits, test results, or other forms of evaluation to confirm that they are meeting their contractual obligations. | AU-6, PS-7, SA- 9 | AU-6, CA-2, CA-7, PS-7, SA-9, SA-11 |\n| Protect | PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users, and processes. | IA-8 | IA-8 |\n| | PR.AC-3: Remote access is managed. | AC-1, AC-19, SC-15 | AC-1, AC-19, SC-15 |\n| | PR.AC-4: Access permissions and authorizations are managed to incorporate the principles of least privilege and separation of duties. | AC-1, AC-2, AC- 3, AC-5, AC-6, AC-16, AC-24 | AC-1, AC-2, AC-3, AC-5, AC-6, AC-16, AC-24 |\n| | PR.AC-6: Identities are proofed and bound to credentials and asserted in interactions. | AC-16, IA-1, IA- 2, IA-4, IA-5, IA- 12, PE-2, PS-3 | AC-16, IA-1, IA-2, IA-4, IA-5, IA-12, PE-2, PS-3 |\n| | 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., individuals' security and privacy risks and other organizational risks)."}], "metadata": {"source": "Introduction to Cybersecurity for Commercial Satellite Operations", "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 Computer Security Division 2015 Annual Report provide? (Part 3)"}, {"role": "assistant", "content": "ues in the Computer Security Division, who provided write-ups on their 2015 project highlights and accomplishments for this annual report (their names are mentioned after each project write-up).\nThe editor would also like to acknowledge Elaine Barker (CSD), Lisa Carnahan (Standards Coordination Office, NIST), Greg Witte and Larry Feldman (G2) for reviewing and providing valuable feedback for this annual report. The editor would also like to acknowledge Kristen Dill of Dill and Company, Inc. for designing the cover and inside layout for this 2015 annual report. ## DI S C L A I M E R\n\nAny mention of commercial products or organizations is for informational purposes only; it is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the products identified are necessarily the best available for the purpose. ## T R A D E M A R K I N F O R M AT I O N\n\nAll names are trademarks or registered trademarks of their respective owners."}], "metadata": {"source": "Computer Security Division 2015 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance):\n\n+ Installation and Execution instructions (for PIV Middleware): The vendor provides technical instructions and other documentation to aid the testing personnel in installing and using the PIV Middleware implementation under test. The PIV Middleware implementation could be in any high-level programming language. Since all the implementations have to be tested from a common test program, the PIV Middleware vendor submitting the product for testing may have to provide Java wrapper programs in some cases to the test facility. The purpose of the wrapper program is to translate the test execution calls made using the test program to the PIV Middleware implementation's native program calls.\n+ Technical documentation (for both PIV Card Application and PIV Middleware): The vendor-supplied technical documentation must include the detailed technical description and the design of the implementation to be tested. This document includes, at a minimum, all the required vendor information specified in DTRs in Appendix A of this document.\n+ Security-related information: The following security related information shall be provided by the vendor: (a) PIV Card Application PIN, (b) PIN Unblocking Key (PUK), (c) Global PIN, (d) pairing code, (e) cryptographic algorithms supported by the card, (f) minutia data, and (g) the number of unsuccessful attempts using (1) wrong PIV Card Application PIN, (2) wrong Global PIN, (3) wrong PUK, (4) and wrong minutia data.\n\nresponse is sent to the vendor. Vendors who object to the results presented in the discrepancy report must explain their reason for the objection. If the reason necessitates another retest, the test laboratory may consider repeating the test. Otherwise, the test lab will seek the guidance of the NIST personnel on the failure before the component is returned to the vendor to be corrected."}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.:\n\nPalo Alto Networks ensures consistent quality management and product security with a wide range of handling policies. All materials related to the production of Palo Alto Networks products must be stored in facilities with strict access controls and 24/7 physical and electronic monitoring. The CM is required to perform complete background, reference, and employment history checks for every candidate before they may access and work on Palo Alto Networks products. CM ICT networks are designed around well-established security standards, including the NIST CSF and ISO/IEC 27001 ix . The CM features a dedicated cybersecurity team and is required to perform regular third-party assessments, including penetration testing and vulnerability assessments. Palo Alto Networks' products are not built or packaged for any particular customer. Rather, the CM prepares prepackaged inventory to satisfy sales forecasts and prevent would-be attackers from targeting specific customers during the production phase."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "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 Best Practices for Privileged User PIV Authentication provide? (Part 5)"}, {"role": "assistant", "content": "Impersonation is usually accomplished by exploiting known weaknesses of password-based single-factor authentication. To greatly reduce the risk of privileged user impersonation to non-national security federal systems, the Cybersecurity Strategy and Implementation Plan (CSIP) [1] published by the Office of Management and Budget (OMB) directs agencies to transition to multi-factor 1 Personal Identity Verification (PIV)-based authentication for all privileged users. This white paper provides additional information regarding this requirement from the CSIP. The purpose of the white paper is to explain the requirement's importance from a security standpoint and to provide best practices for adopting a solution that meets the requirement. ## 1.1 Limitations of Password-Based Single-Factor Authentication\n\nFor many years, most organizations, including federal agencies, have relied heavily on password-based single-factor user authentication. There are many types of threats against this form of authentication, including the following:\n\n- Capturing passwords: an attacker acquiring a password from storage, transmission, or user knowledge and behavior. Examples of ways that attackers capture passwords include the following:\n- o Infecting a system with malware that acts as a keylogger, 2 capturing the user's keystrokes;\n- o Conducting social engineering to trick a user into revealing a password via phishing emails and fraudulent imitation websites, social networks, phone calls, etc.;\n- o Gaining logical or physical access to a system and recovering stored passwords that are unencrypted or weakly encrypted;\n- o Monitoring network traffic and recovering passwords or password hashes that are not adequately protected (e.g., unencrypted, weakly encrypted, replayable);\n- o Watching a user type a password (i.e., shoulder surfing); and\n- o Finding passwords that have been written down on paper, workstations, white boards, etc."}], "metadata": {"source": "Best Practices for Privileged User PIV Authentication", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series:\n\nryptographic literature, where the security requirement for confidentiality assumes that the adversary knows and can even choose (parts of) the plaintext and observe the corresponding ciphertext [14].\nFor an example of a practical attack where the adversary has this power, see the BEAST (Browser Exploit Against SSL/TLS) attack on the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, known in the NVD as CVE-2011-3389 [62]. The OFB and CTR modes in NIST SP 800-38A are not intended to provide any notion of integrity, meaning that they are not secure against adversaries who can modify the ciphertexts. For example, the OFB and CTR modes process every bit of the plaintext separately, so an adversary can make arbitrary changes to bits in the plaintext by flipping the corresponding bits in the ciphertext. This property is explained in Appendix D of NIST SP 800-38A. The same 'bit flipping attack' also applies to the IV of the CBC mode. Indeed, Appendix D of NIST SP 800-38A clarifies that the integrity of the IV used for the CBC mode needs to be protected for this reason. Historically, it was assumed that the CBC and CFB modes do provide some notion of integrity because bit errors in the ciphertext will lead to random errors in at least one block of the plaintext. 3 However, the statement in Appendix D of NIST SP 800-38A that 'the existence of such bit errors may be detected by their randomizing effect on the decryption of the succeeding ciphertext segment' can be misunderstood. More specifically, some integrity protection mechanism against random errors in the plaintext was thought to be sufficient, such as introducing a cyclic redundancy check (CRC) to the plaintext. This is not the case, however, as shown by an attack on the CBC and CFB modes as used in version 1.5 of the Secure Shell (SSH) protocol [37], known as CVE-1999-1085 [59]."}], "metadata": {"source": "Report on the Block Cipher Modes of Operation in the NIST SP 800-38 Series", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\n- o ID.RA-02: Cyber threat intelligence is received from information sharing forums and sources - o ID.RA-03: Internal and external threats to the organization are identified and recorded - o ID.RA-04: Potential impacts and likelihoods of threats exploiting vulnerabilities are identified and recorded - o ID.RA-05: Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization - o ID.RA-06: Risk responses are chosen, prioritized, planned, tracked, and communicated - o ID.RA-07: Changes and exceptions are managed, assessed for risk impact, recorded, and tracked - o ID.RA-08: Processes for receiving, analyzing, and responding to vulnerability disclosures are established - o ID.RA-09: The authenticity and integrity of hardware and software are assessed prior to acquisition and use - o ID.RA-10: Critical suppliers are assessed prior to acquisition - Improvement (ID.IM): Improvements to organizational cybersecurity risk management processes, procedures and activities are identified across all CSF Functions - o ID.IM-01: Improvements are identified from evaluations - o ID.IM-02: Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties - o ID.IM-03: Improvements are identified from execution of operational processes, procedures, and activities - o ID.IM-04: Incident response plans"}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "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 Security Guidelines for Storage Infrastructure:\n\nand network technologies, storage technology has also evolved over the years. Higher capacity storage media and storage system architecture are the two fronts on which storage technology has evolved.\nThe developments on the second front have enabled storage services to support many new and evolving computing use cases but have also introduced storage management complexity and many security challenges."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "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 PDA Forensic Tools_ an Overview and Analysis provide? (Part 5)"}, {"role": "assistant", "content": "## Table of Contents | INTRODUCTION..........................................................................................................................1 | | |---------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| | BACKGROUND............................................................................................................................2 | | | REMOVABLEMEDIA................................................................................................................4 | | | PDAFORENSIC TOOLKITS......................................................................................................6 | | | PDASEIZURE | ..............................................................................................................................6 | | ENCASE........................................................................................................................................7 | | | PALMDD ( PDD ) | .............................................................................................................................7 | | PILOT-LINK | ..................................................................................................................................8 | | POSE............................................................................................................................................8 | | | DUPLICATE DISK (DD )..................................................................................................................9 | | | MISCELLANEOUS TOOLS..............................................................................................................9 | | | SYNOPSIS OF PDASEIZURE..................................................................................................10 | | | POCKET | PC.................................................................................................................................10 | | PALM OS....................................................................................................................................10 | | | ACQUISITION STAGE | ..................................................................................................................12 | | SEARCH FUNCTIONALITY | ..........................................................................................................14 | | GRAPHICS LIBRARY ...................................................................................................................15 | | | BOOKMARKING..........................................................................................................................16 | | | ADDITIONAL TOOLS...................................................................................................................17 | | | REPORT GENERATION................................................................................................................18 | | | PASSWORD CRACKING...............................................................................................................19 | | | SYNOPSIS OF ENCASE............................................................................................................21 | | | ACQUISITION STAGE ..................................................................................................................21 | | | SEARCH FUNCTIONALITY ..........................................................................................................22 | | | SCRIPTS | ......................................................................................................................................25 | | GRAPHICS LIBRARY | ...................................................................................................................26 | | ENSCRIPT &FILTERS.................................................................................................................26 | | | REPORT GENERATION................................................................................................................27 | | | SYNOPSIS OF PDD .....................................................................................................................28 | | | SYNOPSIS OF PILOT-LINK.....................................................................................................29 | | | SYNOPSIS OF DD | .......................................................................................................................30 | | ANALYSIS OVERVIEW...........................................................................................................31 | | | SCENARIOS | .................................................................................................................................31 | | DEVICES | .....................................................................................................................................34 | | PDASEIZURE OUTCOME-POCKETPC............................................................................36 | | | JORNADA 548.............................................................................................................................36 | | | IPAQ 3875/3970/5455"}], "metadata": {"source": "PDA Forensic Tools_ an Overview and Analysis", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.5. 3.2.5) option. 3.2.5) with a non-exportable authentication\nkey (see Sec."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.6. 3.1.6."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Directions in Security Metrics Research:\n\ncom/australia/portals/2/pdf/1650\\_print.pdf\n- [Bel06] Steven Bellovin, On the Brittleness of Software and the Infeasibility of Security Metrics, IEEE Security and Privacy, Volume 4, Issue 4, July-Aug.\n2006\n- [Ber05] Scott Berinato, A Few Good Information Security Metrics, CSO Magazine, July 01, 2005, http://www.csoonline.com/article/220462/A\\_Few\\_Good\\_Information\\_Security \\_Metrics?contentId=220462&slug=&\n- [Bla04] Matt Blaze, Safecracking for the Computer Scientist, Draft Document, December 21, 2004, http://www.crypto.com/papers/safelocks.pdf\n- [Bow02] Jim Bowring, Alessandro Orso, Mary Jean Harrold, Monitoring Deployed on Program Analysis for Software Tools and Engineering, Charleston, South\n- Software Using Software Tomography, ACM SIGPLAN-SIGSOFT Workshop Carolina, November 2002, http://citeseerx.ist.psu.edu/viewdoc/download;jsessionid=A3CE0E004AF88F94 805FBCE9DCFFB558?doi=10.1.1.8.7773&rep=rep1&type=pdf\n- [Bre07] Bill Brenner, Windows Admins Feel Post-Patch Tuesday Pain, SearchSecurity.com, October 19, 2007, http://searchsecurity.techtarget.com/news/article/0,289142,sid14\\_gci1277683,0 0.html\n- [Car08] Lawrence Carin, George Cybenko, Jeff Hughes, Cybersecurity Strategies: The QuERIES Methodology, IEEE Computer, Vol. 41, No. 8, August 2008\n- [CCP06] Common Criteria for Information Technology Security Evaluation Part 1: Introduction and general model, Common Criteria Portal, September 2006, Version 3.1 Revision 1, http://www.commoncriteriaportal.org/files/ccfiles/CCPART1V3.1R1.pdf\n- [CEC91] Information Technology Security Evaluation Criteria (ITSEC), Harmonised Criteria of France - Germany - the Netherlands - the United Kingdom, Commission of the European Communities Directorate XIII/F SOG-IS, June 1991, http://www.iwar.org.uk/comsec/resources/standards/itsec.htm\n- [Cha06] Pravir Chandra, Brian Chess, John Steven, Putting the Tools to Work: How to Succeed with Source Code Analysis, IEEE Security & Privacy, vol. 4, no."}], "metadata": {"source": "Directions in Security Metrics Research", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards:\n\n| Function | Category Unique Identifier | Category |\n|------------|------------------------------|----------------------------------------|\n| Identify | ID. AM | Asset Management |\n| Identify | ID. BE | Business Environment |\n| Identify | ID."}], "metadata": {"source": "Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards", "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 Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\n| PR.AC-1: Identities and credentials are issued, managed, verified, revoked, and audited for authorized devices, users and processes ISO/IEC 27001:2013 A.9.2.1, A.9.2.2, A.9.2.3, A.9.2.4, A.9.2.6, A.9.3.1, A.9.4.2, A.9.4.3 NIST SP 800-53 Rev. 5 AC-1, AC- 2, IA-1, IA-2, IA-3, IA-4, IA-5, IA- 6, IA-7, IA-8, IA-9, IA-10, IA-11 | Most ransomware attacks are conducted through network connections, and ransomware attacks often start with credential compromise (e.g., unauthorized sharing or capture of login identity and password). Proper credential management is essential, although not the only mitigation needed. |\n| Identity Management, Authentication and Access Control (PR.AC): Access to physical and logical assets and associated facilities is limited to authorized users, processes, and devices, and is managed consistent with the assessed risk of unauthorized access to authorized activities and transactions. | PR.AC-3: Remote access is managed ISO/IEC 27001:2013 A.6.2.1, A.6.2.2, A.11.2.6, A.13.1.1, A.13.2.1 NIST SP 800-53 Rev. 5 AC-1, AC- 17, AC-19, AC-20, SC-15 | Most ransomware attacks are conducted remotely. Managing privileges associated with remote access can help maintain the integrity of systems and data files to protect against malicious code insertion and data exfiltration. Using multi-factor authentication is a key - and easily implemented - way to reduce the likelihood of account compromise. |\n| Identity Management, Authentication and Access Control (PR.AC): Access to physical and logical assets and associated facilities is limited to authorized users, processes, and devices, and is managed consistent with the assessed risk of unauthorized access to authorized activities and transactions."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does IT Security for Industrial Control Systems provide? (Part 2)"}, {"role": "assistant", "content": "ing with security professionals to assess the vulnerabilities and establish appropriate strategies for the development of policies to reduce IT security risk within the U.S. process controls industry.\nThe outcome of this work will be the development and dissemination of best practices and ultimately Common Criteria, ISO/IEC 15408 based security specifications that will be used in the procurement, development, and retrofit of industrial control systems. In support of this work this paper addresses the computer control systems used within process control industries, their similarities, and network architectures. A generic set of networking system architectures for industrial process control systems is presented. The vulnerabilities associated with these systems and the IT threats these systems are exposed to are also presented along with a discussion of the Common Criteria and its intended use for these efforts. The current status as well as future efforts of the PCSRF are also discussed. ## Introduction\n\nThe National Institute of Standards and Technology (NIST), Intelligent Systems Division of the Manufacturing Engineering Laboratory is working with the NIST Information Technology Laboratory and the NIST Electrical and Electronics Engineering Laboratory to improve the IT security of networked digital control systems used in industrial applications. This effort is being carried out through the Process Control Security Requirements Forum (PCSRF), an industry group organized under the National Information Assurance Program (NIAP). NIAP is a joint effort between the NIST and the National Security Agency (NSA). As part of the Critical Infrastructure Protection Program, NIST and NSA are working to provide technical support and guidance to industry to improve the Nation's security posture."}], "metadata": {"source": "IT Security for Industrial Control Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 5)"}, {"role": "assistant", "content": "................................................................... | Executive Summary.................................................................................................................\n| Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Control Baselines for Information Systems and Organizations provide?"}, {"role": "assistant", "content": "## Control Baselines for Information Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-53B\n\n\n\n## NIST Special Publication 800-53B\n\n## Control Baselines for Information Systems and Organizations\n\n## JOINT TASK FORCE\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-53B\n\n## October 2020\n\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XI\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems. Such information security standards and guidelines shall not apply to national security systems without the express approval of the appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, OMB Director, or any other federal official."}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Federal Information and Information Systems:\n\nThe minimum security requirements cover seventeen security-related areas with regard to protecting the confidentiality, integrity, and availability of federal information systems and the information processed, stored, and transmitted by those systems. The security-related areas include: (i) access control; (ii) awareness and training; (iii) audit and accountability; (iv) certification, accreditation, and security assessments; (v) configuration management; (vi) contingency planning; (vii) identification and authentication; (viii) incident response; (ix) maintenance; (x) media protection; (xi) physical and environmental protection; (xii) planning; (xiii) personnel security; (xiv) risk assessment; (xv) systems and services acquisition; (xvi) system and communications protection; and (xvii) system and information integrity. The seventeen areas represent a broad-based, balanced information security program that addresses the management, operational, and technical aspects of protecting federal information and information systems.\n\nPhysical and Environmental Protection (PE): Organizations must: (i) limit physical access to information systems, equipment, and the respective operating environments to authorized individuals; (ii) protect the physical plant and support infrastructure for information systems; (iii) provide supporting utilities for information systems; (iv) protect information systems against environmental hazards; and (v) provide appropriate environmental controls in facilities containing information systems.\n\nMEDIA: Physical devices or writing surfaces including, but not limited to, magnetic tapes, optical disks, magnetic disks, Large-Scale Integration (LSI) memory chips, printouts (but not including display media) onto which information is recorded, stored, or printed within an information system."}], "metadata": {"source": "Minimum Security Requirements for Federal Information and Information Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Standard Security Label for GOSIP_ an Invitational Workshop:\n\n3.3.4 Security Tag Type 3 | 4. 3.3.4 Security Tag Type 3 | 4. 3.3.4 Security Tag Type 3 | 4."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Federal Information and Information Systems:\n\nThe minimum security requirements cover seventeen security-related areas with regard to protecting the confidentiality, integrity, and availability of federal information systems and the information processed, stored, and transmitted by those systems. The security-related areas include: (i) access control; (ii) awareness and training; (iii) audit and accountability; (iv) certification, accreditation, and security assessments; (v) configuration management; (vi) contingency planning; (vii) identification and authentication; (viii) incident response; (ix) maintenance; (x) media protection; (xi) physical and environmental protection; (xii) planning; (xiii) personnel security; (xiv) risk assessment; (xv) systems and services acquisition; (xvi) system and communications protection; and (xvii) system and information integrity. The seventeen areas represent a broad-based, balanced information security program that addresses the management, operational, and technical aspects of protecting federal information and information systems. Audit and Accountability (AU): Organizations must: (i) create, protect, and retain information system audit records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful, unauthorized, or inappropriate information system activity; and (ii) ensure that the actions of individual information system users can be uniquely traced to those users so they can be held accountable for their actions."}], "metadata": {"source": "Minimum Security Requirements for Federal Information and Information Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Computer Security Division 2007 Annual Report:\n\nTo keep pace with the rate of change in emerging technologies, we conduct a large amount of research in existing and emerging technology areas. Some of the many topics we research include smart card infrastructure and security, wireless and mobile device security, Voice over IP security issues, digital forensics tools and methods, access control and authorization management, Internet Protocol security, intrusion detection systems, quantum information system security and quantum cryptography, and vulnerability analysis. Our research helps to fulfill specific needs by the federal government that would not be easily or reliably filled otherwise.\n\n## Digital Handheld Device Forensics\n\nCell phones are ubiquitous today, used by individuals for both personal and professional purposes. Because of their pervasiveness and information content, cell phones are an emerging but rapidly growing area of computer forensics. Besides placing calls, cell phones can allow users to perform additional tasks such as Short Message Service (SMS) messaging, Multimedia Messaging Service (MMS) messaging, Instant Messaging (IM), e-mail exchange, Web browsing, Personal Information Management (PIM) administration (e.g., address book, task list, and calendar schedule), photo and video capture, and even the reading, editing, and production of digital documents. Over time, a significant amount of information tends to accumulate on them that may be connected with an incident or crime and recovered during an investigation."}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "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 Stateless Hash-Based Digital Signature Standard provide? (Part 5)"}, {"role": "assistant", "content": "eral Information Processing Standard (FIPS) publication,\n- b. Adopted in a FIPS or NIST recommendation, or\n- c. Specified in the list of approved security functions in SP 800-140C. 10. Export Control.\nCertain cryptographic devices and technical data regarding them are subject to federal export controls. Exports of cryptographic modules that implement this standard and technical data regarding them must comply with these federal regulations and be licensed by the Bureau of Industry and Security of the U.S. Department of Commerce. Information about export regulations is available at https://www.bis.doc.gov. 11. Patents. The algorithm in this standard may be covered by U.S. or foreign patents. 12. Implementation Schedule. This standard becomes effective immediately upon final publication. 13. Specifications. Federal Information Processing Standard (FIPS) 205, Stateless Hash-Based Digital Signature Standard (affixed). 14. Qualifications. The security of a digital signature system depends on the secrecy of the signatory's private keys. Signatories shall , therefore, guard against the disclosure of their private keys. While it is the intent of this standard to specify general security requirements for generating digital signatures, conformance to this standard does not ensure that a particular implementation is secure. It is the responsibility of an implementer to ensure that any module that implements a digital signature capability is designed and built in a secure manner. Similarly, the use of a product containing an implementation that conforms to this standard does not guarantee the security of the overall system in which the product is used. The responsible authority in each agency or department shall ensure that an overall implementation provides an acceptable level of security."}], "metadata": {"source": "Stateless Hash-Based Digital Signature Standard", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management:\n\nroom number).. | To ensure that managers can find the device to revalidate it for supply chain risk management. • Remove it if unauthorized |\n| The period of time the device is authorized.\nLocal enhancements might include: • When the device must be physically inspected/verified for supply chain risk management | To allow previously authorized devices to remain in the authorized hardware inventory, but know such devices are no longer authorized. |\n| Expected status of the device (e.g., authorized, expired, pending approval, missing) to include: • Date first authorized; • Date of most recent authorization; and • Date authorization revoked. Local enhancements might include: • Returned from high-risk location; • Removed pending reauthorization; and • Date of last status change. | To determine which devices in the authorized hardware inventory are not likely to be found in actual state inventory. |"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective:\n\n'America's economic prosperity, national security, and our individual liberties depend on our commitment to securing cyberspace and maintaining an open, interoperable, secure, and reliable Internet. Our critical infrastructure continues to be at risk from threats in cyberspace, and our economy is harmed by the theft of our intellectual property. Although the threats are serious and they constantly evolve, I believe that if we address them effectively, we can ensure that the Internet remains an engine for economic growth and a platform for the free exchange of ideas.' 1\n\nCyber Incident Management standards support information sharing processes, products, and technology implementations for cyber incident identification, handling, and remediation. Such standards enable organizations to identify when a cyber incident has occurred, to properly respond to that incident and recover from any losses as a result of the incident. Such standards are one method to enable jurisdictions to exchange information about incidents, vulnerabilities, threats and attacks, the system(s) that were exploited, security configurations and weaknesses that could be exploited, etc.\n\nSecurity Automation and Continuous Monitoring (SACM) s tandards describe protocols and data formats that enable the ongoing, automated collection, monitoring, verification, and maintenance of software, system, and network security configurations, and provide greater awareness of vulnerabilities and threats to support organizational risk management decisions. Automation protocols also include standards for machine-readable vulnerability identification and metrics, platform and asset identification, actionable threat information and policy triggers for actions to respond to threats and policy violations. Automated activities would include a Security Operation Center (SOC) to ensure autonomous and continuing monitoring and evolution of the security state of assets based upon prescribed events."}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\n| DTR No: | DTR Description | Spec. Reference |\n|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|\n| | common-derived-pivAuth (OID = 2.16.840.1.101.3.2.1.3.40) or id-fpki-common- derived-pivAuth-hardware (OID = 2.16.840.1.101.3.2.1.3.41). | Authentication Certificate Profile |\n| DTR-07.03.01.07 | The subjectAltName extension shall include a UUID encoded as a URN, as specified in Section 3 of [RFC4122], A Universally Unique IDentifier (UUID) URN Namespace . | • [PROF], Worksheet titled - Derived PIV Authentication Certificate Profile |\n| DTR-07.03.01.08 | The piv-interim extension (OID = 2.16.840.1.101.3.6.9.1) shall be present and contain an interim_indicator field, which is populated with a Boolean value. This extension is not critical. | • [PROF], Worksheet titled - Derived PIV Authentication Certificate Profile |\n| DTR-07.03.01.09 | The authorityInfoAccess field shall contain an id-ad-ocsp accessMethod."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nIMDs are tiny computing platforms that run firmware in extremely power constrained environments. They offer data storage for static data (such as device information), relatively static data (such as patient identification, medical condition, therapy configuration) and dynamic data (such as recent patient readings and audit logs). IMDs offer wireless access for read and write operations to the data on the IMD (including the firmware) to a variety of stakeholders and roles.\n\nSome of the threats to wireless IMDs include device reprogramming, data extraction, data tampering, repeated access attempts and data flooding. Vulnerabilities include unsecured communication channels, inadequate authentication and access control, weak audit mechanisms and meager storage. The resulting risks include patient safety compromise resulting from firmware malfunction or therapy misconfiguration, device unavailability due to battery power depletion, patient privacy loss due to data leakage to unauthorized parties, and inappropriate medical follow-up due to tampering of patient readings. While some cyber threats may be unintentional, various motivations exist for deliberate cyber attacks, such as patient information gathering, negative impact to patient health status, ego satisfaction of the attacker, as well as gaining competitive advantage over another vendor through negative press.\n\nIdentification of the various data types within an IMD is an essential step in analyzing the security and privacy risks of such devices. Possible data types include firmware (though technically not 'data'), device identification data, patient identification and health condition data, therapy configuration data, patient readings, audit log data, and other data."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\n.................................................................... | LIST OFTABLES....................................................................................................................\n| VIII |\n| EXECUTIVE SUMMARY........................................................................................................... | EXECUTIVE SUMMARY........................................................................................................... | 1 |\n| 1. INTRODUCTION.................................................................................................................. | 1. INTRODUCTION.................................................................................................................. | 1 |\n| 1.1 | PURPOSEAND SCOPE ......................................................................................................... | 1 |\n| 1.2 | AUDIENCEAND ASSUMPTIONS .........................................................................................."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to LTE Security:\n\ncellular security; networking; Long Term Evolution; 3 rd Generation Partnership Project (3GPP); LTE; telecommunications; wireless.\n\nThis document introduces high-level LTE concepts and discusses technical LTE security mechanisms in detail. Technical readers are expected to understand fundamental networking concepts and general network security. It is intended to assist those evaluating, adopting, and operating LTE networks, specifically telecommunications engineers, system administrators, cybersecurity practitioners, and security researchers.\n\nThe mobile device hardware, mobile operating system (e.g., Android, Blackberry, iOS, Windows Phone), and 3rd party mobile applications are generally out of the scope of this document unless otherwise noted. This document does not analyze non 3rd Generation Partnership Project (3GPP) networks (e.g., WiFi, WiMAX, 3GPP2), forthcoming 3GPP features such as device to device cellular communications and cellular internet of things (IoT), and the over-the-air (OTA) management updates to cellular platforms, and the networks supporting services (e.g Domain Name Services (DNS), Network Time Protocol (NTP)). Supply chain issues relating to cellular networks are also not described. Finally, the IP Multimedia Subsystem (IMS), a modern platform for delivering services such as Voice over LTE (VoLTE), is not included within this document."}], "metadata": {"source": "Guide to LTE 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 Risk Assessment?"}, {"role": "assistant", "content": "According to 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report:\n\n| | Introduction: Workshop Objective, Participants, and Agenda.......................................1 |\n|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| | Workshop Session Highlights and Summaries................................................................5 |\n| HPC | Architecture and Security Posture ........................................................................5 |\n| | HPC Operator Security Experience...............................................................................6 |\n| | Risk Management Framework Development, Implementation, and Assessment.........7 |\n| 2.3.1."}], "metadata": {"source": "3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to 2016 NIST_ITL Cybersecurity Program Annual Report:\n\n| ACKNOWLEDGMENTS...................................................................................................................................................................V | ACKNOWLEDGMENTS...................................................................................................................................................................V | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | TRADEMARK INFORMATION.........................................................................................................................................................V | TRADEMARK INFORMATION.........................................................................................................................................................V | | WELCOME LETTER..........................................................................................................................................................................1 | WELCOME LETTER..........................................................................................................................................................................1 | | BACKGROUND INFORMATION OF ANNUAL REPORT.................................................................................................................."}], "metadata": {"source": "2016 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface:\n\n3.1.2. 3.1.2. 3.1.2 and 3."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "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 Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards provide? (Part 4)"}, {"role": "assistant", "content": "lifecycle for cybersecurity risk. Underlying the five concurrent Functions, the Core identifies 23 Categories (as shown in Table 1) and 108 Subcategories that describe discrete cybersecurity outcomes.\nThe Core also presents informative references for each of the Subcategories that include industry standards, guidelines, and practices. Table 1 - CSF Functions and Categories\n\n| Function | Category Unique Identifier | Category |\n|------------|------------------------------|----------------------------------------|\n| Identify | ID. AM | Asset Management |\n| Identify | ID. BE | Business Environment |\n| Identify | ID."}], "metadata": {"source": "Benefits of an Updated Mapping between the NIST Cybersecurity Framework and the NERC Critical Infrastructure Protection Standards", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to a Secure Enterprise Network Landscape provide? (Part 4)"}, {"role": "assistant", "content": "NA]), and the evolving wide area network (WAN) infrastructure to provide a comprehensive set of security services for the modern enterprise network landscape (e.g., secure access service edge [SASE]).\n## Keywords\n\ncloud access security broker (CASB); firewall; microsegmentation; secure access service edge (SASE); secure web gateway (SWG); security orchestration, automation, and response (SOAR); software-defined perimeter (SDP); software-defined wide area network (SD-WAN); virtual private network (VPN); zero trust network access (ZTNA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| Practice | Task | Priority | Recommendations [R], Considerations [C], and Notes [N] Specific to AI Model Development | Informative References | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------| | | | | R4: Permit indirect access only to model weights."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Capability Core Baseline:\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Karen Scarfone Matthew Smith\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\n\n\n## NISTIR 8259A\n\n## IoT Device Cybersecurity Capability Core Baseline\n\nMichael Fagan Katerina N. Megas Applied Cybersecurity Division Information Technology Laboratory\n\nKaren Scarfone Scarfone Cybersecurity Clifton, VA\n\nMatthew Smith Huntington Ingalls Industries Annapolis Junction, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nMay 2020\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8259A 23 pages (May 2020)\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259A\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "IoT Device Cybersecurity Capability Core Baseline", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guidelines for API Protection for Cloud-Native Systems provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-228\n\n## Guidelines for API Protection for Cloud-Native Systems\n\nRamaswamy Chandramouli Zack Butcher\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-228\n\n\n\n## NIST Special Publication 800 NIST SP 800-228\n\n## Guidelines for API Protection for Cloud-Native Systems\n\nRamaswamy Chandramouli Computer Security Division Information Technology Laboratory\n\nZack Butcher Tetrate, Inc. This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-228\n\nJune 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nNational Institute of Standards and Technology Craig Burkhardt, Acting Under Secretary of Commerce for Standards and Technology and Acting NIST Director\n\nCertain 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": "Guidelines for API Protection for Cloud-Native Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 A Framework for Designing Cryptographic Key Management Systems:\n\n| Controlling Human Input ...............................................................................\n| 58 |\n| 6.7.4 | 6.7.4 | Multiparty Control.......................................................................................... | 58 |\n| 6.7.5 | 6.7.5 | Key Splitting .................................................................................................. | 59 |\n| 6.8 Compromise Recovery ......................................................................................... | 6.8 Compromise Recovery ......................................................................................... | 6.8 Compromise Recovery ........................................................................................."}], "metadata": {"source": "A Framework for Designing Cryptographic Key Management 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 Access Control?"}, {"role": "assistant", "content": "According to Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992:\n\n| 5.1 Kerberos Authentication/Access Control System - Jeff Schiller, Massachusetts | | | 5.2 | 5.2 | tute of Technology Supercomputer Center Access Control Requirements, Dan Nessett, Lawrence Liver- more National Laboratory | 16 20 | | 5.3 | 5.3 | General Discussion on Access Control | 22 | | 6 | 6 | | 27 | | | Session on Application Security in Distributed Networks | Session on Application Security in Distributed Networks | | | 6.1 | 6.1 | Center 6.2 An Overview of Internet Privacy Enhanced Mail - Steve Kent, Bolt, Beranek, and Newman | 27 30 | | 6.3 | 6.3 | Security in Open Systems Technology Demonstrator Programme - John Laws, Defence Research Agency, UK | 35 | | 7 | | | 38 | | 7.1 | 7.1 | Session on Security Mcmagement in Distributed Networks SDNS Security Management - Wayne Jansen, National Institute of Standards and Technology | 38 | | 7.2 | 7.2 | FIRST System - Dennis Steinauer, National Institute of Standards and Technology | 41 | | 7.3 | 7.3 | CERT Activities - Dain Gary, Software Engineering Institute, Carnegie-Mellon Uni- versity | 43 | | 8 | Session on"}], "metadata": {"source": "Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 1 – General:\n\nd for the protection of sensitive, unclassified government information. 2. They often establish some level of interoperability between different systems that implement the NIST standards.\nFor example, two products that both implement the Advanced Encryption Standard (AES) 10 cryptographic algorithm have the potential to interoperate, provided that the other functions of the product are compatible. 3. They often provide for scalability because the U.S. government requires products and techniques that can be effectively applied in large numbers. 4. They are scrutinized by U.S. government experts and the public to ensure that they provide a high level of security. The NIST standards process invites broad public participation, not only through the formal NIST public review process before adoption but also by interaction with the open cryptographic community through NIST workshops, participation in voluntary standards development organizations, participation in cryptographic research conferences, and informal contacts with researchers. NIST encourages the study and"}], "metadata": {"source": "Recommendation for Key Management_ Part 1 – General", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n3.2.1, Appendix F. 3.2.1 [NIST-SP800-53r5] CP-2, CP-3, IR-3, IR-8 [NIST-SP800-61r2] |\n| RS."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "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 is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n3.2.5. 3.2.5."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2007 Annual Report:\n\n53 | | Computer Security Division Publications - FY 2007 | 54 | | Ways to Engage Our Division and NIST | 56 |"}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1:\n\n| XCCDF Fact | Description of Use |\n|------------------------------------------|---------------------------------------------------------------|\n| urn:scap:fact:asset:identifier:mac | Ethernet media access control address |\n| urn:scap:fact:asset:identifier:ipv4 | Internet Protocol version 4 address |\n| urn:scap:fact:asset:identifier:ipv6 | Internet Protocol version 6 address |\n| urn:scap:fact:asset:identifier:host_name | Host name of the asset, if assigned |\n| urn:scap:fact:asset:identifier:fqdn | Fully qualified domain name |\n| urn:scap:fact:asset:identifier:ein | Equipment identification number or other inventory tag number |"}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case:\n\nAlpha has ten full-time employees, and six of those are machine operators. Alpha has no fulltime control system engineers, or on-site IT or operational technology (OT) personnel. None of the employees have any formal cybersecurity training.\n\nAdditionally, personnel security is addressed through pre-employment screenings, adequate position descriptions, terms of employment, and cybersecurity education and training. Additional details regarding physical security requirements are mentioned in Section 3.2.6 Physical Security of the Cybersecurity Policy.\n\n## Cybersecurity Awareness Training"}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "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 Security Recommendations for Server-based Hypervisor Platforms provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-125A Revision 1\n\n## Security Recommendations for Server-based Hypervisor Platforms\n\nRamaswamy Chandramouli\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-125Ar1\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-125A\n\n## Revision 1\n\n## Security Recommendations for Server-based Hypervisor Platforms\n\nRamaswamy Chandramouli Computer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-125Ar1\n\nJune 2018\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official."}], "metadata": {"source": "Security Recommendations for Server-based Hypervisor Platforms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight:\n\nsistent set of indicators. Status could be a simple indicator (e.g., open, closed, pending, waived, transferred) or provide a more detailed explanation (e.g., 'risk accepted pending review by the Jan.\n24 quarterly risk committee meeting')."}], "metadata": {"source": "Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Representation of PIV Chain-of-Trust for Import and Export:\n\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|\n| | 1.1 | Background..................................................................................................... 1 |\n| | 1.2 Purpose and Scope | ........................................................................................ 1 |\n| | 1.3 Document | Structure........................................................................................"}], "metadata": {"source": "Representation of PIV Chain-of-Trust for Import and Export", "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 Security Considerations for Remote Electronic UOCAVA Voting provide? (Part 2)"}, {"role": "assistant", "content": "ments, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, organizations may wish to closely follow the development of these new publications by NIST.\n## TABLE OF CONTENTS\n\n| 1 INTRODUCTION .......................................................................... 1 | 1 INTRODUCTION .......................................................................... 1 | 1 INTRODUCTION .......................................................................... 1 |\n|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSE AND SCOPE......................................................................2 | |\n| 1.2 | INTENDED AUDIENCE ......................................................................2 | |\n| 1.3 | ORGANIZATION.............................................................................2 | |\n| 2 GENERAL ARCHITECTURE............................................................ 4 | 2 GENERAL ARCHITECTURE............................................................ 4 | 2 GENERAL ARCHITECTURE............................................................"}], "metadata": {"source": "Security Considerations for Remote Electronic UOCAVA Voting", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Guide to Storage Encryption Technologies for End User Devices:\n\n3.3.3 Use Case 3: Sharing Data with Contractor... 3.3.3 Use Case 3: Sharing Data with Contractor\n\nA user wants to provide a contractor with copies of large data sets on a daily basis because the contractor has no direct access to the system containing the data."}], "metadata": {"source": "Guide to Storage Encryption Technologies for End User Devices", "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 Planning?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts, practices, and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nassess; authorization to operate; authorization to use; authorizing official; categorize; common control; common control authorization; common control provider; continuous monitoring; control assessor; control baseline; cybersecurity framework profile; hybrid control; information owner or steward; information security; monitor; ongoing authorization; plan of action and milestones; privacy; privacy assessment report; privacy control; privacy plan; privacy risk; risk assessment; risk executive function; risk management; risk management framework; security; security assessment report; security control; security engineering; security plan; security risk; senior agency information security officer; senior agency official for privacy; supply chain risk management; system development life cycle; system owner; system privacy officer; system security officer; system-specific control.\n\n'… Effective management of cybersecurity risk requires that agencies align information security management processes with strategic, operational, and budgetary planning processes…'"}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.2.5, 3. 3.2.5, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Report of the Workshop on Cryptography in Support of Computer Security provide? (Part 2)"}, {"role": "assistant", "content": "21-22, 1976. The workshop was organized to obtain expert opinions on the mathematical and statistical characteristics of the proposed Data Encryption Standard (DES) as it relates to computer security.\nThis report summarizes formal presentations that were made, outlines major issues that were raised, quotes statements that were made for the record and answers several of the major ques- tions that were asked. Key words: Cryptanalysis ; cryptography; encryption; key management; known plaintext attack; security; work factor. ## 1 . EXECUTIVE SUMMARY\n\n## 1 . 1 Organization\n\n1 . The workshop was divided into three time periods introduction, parallel working sessions, and summary. 2. A total of 42 people attended from the Federal Government, industry and universities. 3. The workshop chairman was Professor Julian Bigelow, the Mathematics group leader was Dr. Howard Campaigne and the Applications group leader was Dr. Joseph Eachus. ## 1.2 Introductory Session\n\n1. The purposes of the introductory session were to introduce the objectives of the workshop, i.e., to analyze the mathematical and statistical characteristics of the proposed Data Encryption Standard (DES); to provide a forum for identifying potential weaknesses of the DES; and to develop procedures for generating and distributing keys. 2. Individual participants presented a description of the DES, the results of a previous NBS sponsored workshop on technology affecting the DES, and preliminary analysis of the DES. 3. Professor Martin Heilman, of Stanford University, presented a prepared statement. 4. Mr. John Scantlin, of the Lexar Corp., submitted for distribution a written paper which analyzed the DES. ## 1.3 Mathematics Working Group\n\n1. The mathematics working group discussed potential weaknesses of the DES, such as the limitations in key length, the non-random structure of the S-boxes, and possible vulnerabilities to less than exhaustion atacks. 2."}], "metadata": {"source": "Report of the Workshop on Cryptography in Support of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nncy official with statutory or operational authority for specified information and responsibility for establishing the controls for its generation, collection, processing, dissemination, and disposal.\nThe information owner has the following responsibilities related to system security plans:\n\n| CLASS | FAMILY | IDENTIFIER |\n|-------------|--------------------------------------------------------|--------------|\n| Management | Risk Assessment | RA |\n| Management | Planning | PL |\n| Management | System and Services Acquisition | SA |\n| Management | Certification, Accreditation, and Security Assessments | CA |\n| Operational | Personnel Security | PS |\n| Operational | Physical and Environmental Protection | PE |\n| Operational | Contingency Planning | CP |\n| Operational | Configuration Management | CM |\n| Operational | Maintenance | MA |\n| Operational | System and Information Integrity | SI |\n| Operational | Media Protection | MP |\n| Operational | Incident Response | IR |\n| Operational | Awareness and Training | AT |\n| Technical | Identification and Authentication | IA |\n| Technical | Access Control | AC |\n| Technical | Audit and Accountability | AU |\n| Technical | System and Communications Protection | SC |\n\n| Configuration Control [CNSS Inst."}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nFISMA requires federal agencies to implement appropriate controls to protect federal\ninformation and information systems from unauthorized access, use, disclosure,\ndisruption, or modification. The NIST RMF [NISTRMF] provides a process that integrates\nsecurity, privacy, and cyber supply chain risk management activities into the system\ndevelopment life cycle. It is expected that federal agencies and organizations that\nprovide services under these guidelines have already implemented the controls and\nprocesses required under FISMA and associated NIST risk management processes and\npublications."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\n| 4.7 | Interrelationships among Policies ................................................................. | Interrelationships among Policies ................................................................. | 25 |\n|-------|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|\n| 4.8 | Personal Accountability................................................................................. | Personal Accountability................................................................................. | 26 |\n| 4.9 | Anonymity, Unlinkability, and Unobservability............................................... | Anonymity, Unlinkability, and Unobservability..............................................."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guide to Security for Full Virtualization Technologies:\n\n-  Phase 1: Initiation. This phase includes the tasks that an organization should perform before it starts to design a virtualization solution. These include identifying needs for virtualization, providing an overall vision for how virtualization solutions would support the mission of the organization, creating a high-level strategy for implementing virtualization solutions, developing virtualization policy, identifying platforms and applications that can be virtualized, and specifying business and functional requirements for the solution.\n-  Phase 2: Planning and Design. In this phase, personnel specify the technical characteristics of the virtualization solution and related components. These include the authentication methods and the cryptographic mechanisms used to protect communications. At the end of this phase, solution components are procured.\n-  Phase 3: Implementation. In this phase, equipment is configured to meet operational and security requirements, installed and tested as a prototype, and then activated on a production network. Implementation includes altering the configuration of other security controls and technologies, such as security event logging, network management, and authentication server integration.\n-  Phase 4: Operations and Maintenance. This phase includes security-related tasks that an organization should perform on an ongoing basis once the virtualization solution is operational, including log review, attack detection, and incident response.\n-  Phase 5: Disposition. This phase encompasses tasks that occur when a virtualization solution is being retired, including preserving information to meet legal requirements, sanitizing media, and disposing of equipment properly."}], "metadata": {"source": "Guide to Security for Full Virtualization Technologies", "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 IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\n3.5.3."}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\nimplementing processes that may serve as inputs into an information security measurement program, ensuring that data gathering and reporting are clearly defined helps facilitate valid data collection.\nHaving a validation process in place to check the integrity, accuracy, and structure of the data provides a way to address potential errors before any analysis is done. By setting a standard process to validate data, an organization can have a repeatable way to look at the data and ensure its quality."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to An Introduction to Privacy Engineering and Risk Management in Federal Systems:\n\nTo support agencies' ability to conduct privacy engineering, this publication introduces a set of privacy engineering objectives-predictability, manageability, and disassociability-to help system engineers focus on the types of capabilities the system needs in order to demonstrate how an agency's privacy policies and system privacy requirements have been implemented. In addition, this report introduces a privacy risk model to enable agencies to conduct more consistent privacy risk assessments based on the likelihood that an operation performed by a system would create a problem for individuals when processing PII-a problematic data action-and the impact of the problematic data action should it occur.\n\n'They [the FIPPs] are value statements rather than recipes, however. System planners often encounter difficulties when trying to operationalize them, particularly when assessing privacy risks and when establishing privacy requirements for designing and developing systems and technologies. Those activities require a well-articulated set of privacy objectives and a privacy risk assessment approach, from which privacy risks can be evaluated and implementation requirements can be developed.' 35\n\nNIST has developed guidance for information security risk management-including the RMF, and guidance on risk assessment-which has informed much of the approach introduced in this report. 44 Although the concept of privacy risk is not new to federal policy, to date there has been no guidance on how to assess this risk. 45 Outside the federal government, standards such as the International Organization for Standardization (ISO) Privacy Framework and the Organization for the Advancement of Structured Information Standards (OASIS) Privacy Management Reference Model include provisions for privacy risk assessment as part of their frameworks or methodologies, but they do not provide guidance on how to actually conduct a risk assessment"}], "metadata": {"source": "An Introduction to Privacy Engineering and Risk Management in Federal Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nDigital Identity Guidelines\n\nDigital Identity Guidelines\n\nTemoshok D, Galluzzo R, LaSalle C, Lefkovitz N, Regenscheid A, Choong YY, Proud-\nMadruga D, Gupta S (2025) Digital Identity Guidelines. (National Institute of Standards\nand Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-63-4.\nhttps://doi.org/10.6028/NIST.SP.800-63-4"}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Glossary of Computer Security Terminology:\n\nThis National Institute of Standards and Technology Interagency Report (NISTIR) presents a glossary of computer security terminology, whose development was sponsored under the auspices of the National Security Telecommunications and Information Systems Security Committee (NSTISSC) . This glossary is a collection of terms and definitions used by various federal departments and agencies in their policies, standards, and other publications. This glossary did not seek to arrive at a single agreed-upon definition of each entry; therefore, some definitions may not be wholly consistent. Although never formally issued by the NSTISSC, since the document does reflect actual usage of these terms, it may provide a useful reference source to the computer security practitioner\n\nNIST expresses its appreciation to the Subcommittee on Information Systems Security (SISS) and the Executive Secretariat of the National Security Telecommunications and Information Systems Security Committee for their kind permission to publish this report. We also wish to acknowledge the many computer security professionals who participated in the development of this glossary. - 2) The official authorization granted to an information system to process sensitive information in its operational environment based on comprehensive security evaluation of the system's hardware, firmware, and software security design, configuration and implementation and of the other system procedural, administrative, physical, TEMPEST, personnel and communications security controls. (APR 700-10)\n- 3) The authorization and approval granted to a system or network to process classified or sensitive data. Accreditation will be made on the basis of certification by a competent authority that designated technical personnel have verified that specified technical requirements for achieving adequate data security have been met."}], "metadata": {"source": "Glossary of Computer Security Terminology", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Approaches for Federal Agencies to Use the Cybersecurity Framework:\n\n----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Framework Profile.\nPrimary Cybersecurity Framework Components: Core, Profile(s) Summary: Federal agencies can use the Cybersecurity Framework Core Subcategories to align and merge cybersecurity requirements that may overlap or fall between offices in the organizational structure. This reconciliation helps to ensure compliance and prioritize requirements across the organization using the subcategory outcomes. This becomes a means of operationalizing cybersecurity | Framework Profile. Primary Cybersecurity Framework Components: Core, Profile(s) Summary: Federal agencies can use the Cybersecurity Framework Core Subcategories to align and merge cybersecurity requirements that may overlap or fall between offices in the organizational structure. This reconciliation helps to ensure compliance and prioritize requirements across the organization using the subcategory outcomes. This becomes a means of operationalizing cybersecurity |\n| activities and a tool for iterative, dynamic, and prioritized risk management for the agency. Typical Participants: Risk Executive, Chief Information Officer (CIO), Senior Information Security | activities and a tool for iterative, dynamic, and prioritized risk management for the agency."}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "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 Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n| PO.2.1: Create new roles and alter responsibilities for existing roles as needed to encompass all parts of the SDLC. Periodically review and maintain the defined roles and responsibilities, updating them as needed. | High | R1: Include AI model development security in SDLC-related roles and responsibilities throughout the SDLC. The roles and responsibilities should include, but are not limited to, AI model development, AI model operations, and data science. N1: Roles and responsibilities involving AI system producers, AI model producers, and other third-party providers can be documented in agreements. | AI RMF: Govern 2.1 |\n| Implement Roles and Responsibilities (PO.2): Ensure that everyone inside and outside of the organization involved in the SDLC is prepared to perform their SDLC-related roles and responsibilities throughout the SDLC. | PO.2.2: Provide role-based training for all personnel with responsibilities that contribute to secure development. Periodically review personnel proficiency and role-based training, and update the training as needed. | High | R1: Role-based training should include understanding cybersecurity vulnerabilities and threats to AI models and their possible mitigations. | AI RMF: Govern 2.2 OWASP: LLM04-7 |\n| Implement Roles and Responsibilities (PO.2): Ensure that everyone inside and outside of the organization involved in the SDLC is prepared to perform their SDLC-related roles and responsibilities throughout the SDLC. | PO.2.3: Obtain upper management or authorizing official commitment to secure development, and convey that commitment to all with development- related roles and responsibilities. | Medium | R1: Leadership should commit to secure development practices involving AI models."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\n| Category | Subcategory and Selected Informative References | Ransomware Application | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Protect | Protect | Protect | | Identity Management, Authentication and Access Control (PR.AC): Access to physical and logical assets and associated facilities is limited to authorized users, processes, and devices, and is managed consistent with the assessed risk of unauthorized access to authorized activities and transactions."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Reference Architecture:\n\n1. Architecture (e.g., diversity, complexity, provenance, multi-tenancy, data segregation). Architecture challenges in cloud forensics include:\n2. o Dealing with variability in cloud architectures between providers\n3. o Tenant data compartmentalization and isolation during resource provisioning\n4. o Proliferation of systems, locations, and endpoints that can store data\n5. o Accurate and secure provenance for maintaining and preserving chain of custody\n2. Data collection (e.g., data integrity, data recovery, data location, imaging). Data collection challenges in cloud forensics include:\n7. o Locating forensic artifacts in large, distributed, and dynamic systems\n8. o Locating and collecting volatile data\n9. o Data collection from virtual machines\n10. o Data integrity in a multi-tenant environment where data is shared among multiple computers in multiple locations and accessible by multiple parties\n11. o Inability to image all of the forensic artifacts in the cloud\n12. o Accessing the data of one tenant without breaching the confidentiality of other tenants\n13. o Recovery of deleted data in a shared and distributed virtual environment\n3. Analysis (e.g., correlation, reconstruction, time synchronization, logs, metadata, timelines). Analysis challenges in cloud forensics include:\n15. o Correlation of forensic artifacts across and within cloud providers\n16. o Reconstruction of events from virtual images or storage\n17. o Integrity of metadata\n\n- o Timeline analysis of log data, including synchronization of timestamps\n4. Anti-forensics (e.g., obfuscation, data hiding, malware). Anti-forensics is a set of techniques used specifically to prevent or mislead forensic analysis. Anti-forensic challenges in cloud forensics include:\n- o The use of obfuscation, malware, data hiding, or other techniques to compromise the integrity of evidence\n- o Malware may circumvent virtual machine isolation methods\n5."}], "metadata": {"source": "NIST Cloud Computing Forensic Reference Architecture", "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 Recommendations for Federal Vulnerability Disclosure Guidelines provide? (Part 2)"}, {"role": "assistant", "content": "aft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2023-05-17\n\n## How to Cite this NIST Technical Series Publication:\n\nSchaffer K, Mell P, Trinh H, Van Wyk I (2023) Recommendations for Federal Vulnerability Disclosure Guidelines. (National Institute of Standards and Technology, Gaithersburg, MD), NIST (Special Publication) NIST SP 800-216."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0 provide?"}, {"role": "assistant", "content": "## NISTIR 6985\n\n## COTS Security Protection Profile - Operating Systems (CSPP-OS)\n\n(Worked Example Applying Guidance of NISTIR-6462, CSPP)\n\nVersion 1.0\n\n## Gary Stoneburner\n\nU.S. DEPARTMENT OF COMMERCE Technology Administration National Institutes of Standards and Technology Gaithersburg, MD 20899\n\nApril 2003\n\n\n\nU.S. DEPARTMENT OF COMMERCE Donald L. Evans, Secretary\n\nTECHNOLOGY ADMINISTRATION Phillip J. Bond, Under Secretary of Commerce for Technology\n\nNATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arden L. Bement, Jr., Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This NIST Interagency Report (NISTIR) reports on ITL's research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations. 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. National Institute of Standards and Technology Interagency Report 6985 Natl. Inst. Stand."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Information Security Guide for Government Executives:\n\n| Information Security Program Elements | Information Security Program Elements | |--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Certification, Accreditation, and Security Assessments | Security certification and accreditation (C&A) are important activities that support a risk management process, and each is an integral part of an agency's information security program."}], "metadata": {"source": "Information Security Guide for Government Executives", "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 General Procedures for Registering Computer Security Objects:\n\n- (a) mechanisms for maintaining the integrity and confidentiality of the registration database including adequate backup;\n- (b) the design of appropriate forms (paper, electronic or both), containing the data elements specified;\n- (c) a process for auditing the registration database and financial accounts;\n- (d) management of the object name space.\n\nThis section shall cover object usage rules, handling instructions, and implementation details or restrictions beyond those imposed by the base standard. The text in this section may be used to clarify security tag information appearing in the Format Table. Examples are error conditions and their required system response such as return of an error response and local event auditing. The processing rules in Appendix B of the Standard Security Label FIPS may be referenced in this section. Explicit omissions, additions, or refinements to the processing rules in the SSL document also must appear in this section."}], "metadata": {"source": "General Procedures for Registering Computer Security Objects", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Security for Full Virtualization Technologies provide? (Part 3)"}, {"role": "assistant", "content": "m individuals and organizations whose comments improved the overall quality of this publication. ## Trademark Information\n\nAll names are trademarks or registered trademarks of their respective owners.\n## Table of Contents\n\n| Executive Summary............................................................................................................ES-1 | Executive Summary............................................................................................................ES-1 | Executive Summary............................................................................................................ES-1 | |\n|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction | ................................................................................................................... 1-1 | ..................................................................................................................."}], "metadata": {"source": "Guide to Security for Full Virtualization Technologies", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n## Personal Identity Verification (PIV) of Federal Employees and Contractors\n\n## Category: Information Security Subcategory: Identity\n\nAuthentication of an individual's identity is a fundamental component of physical and logical access control. An access control decision must be made when an individual attempts to access security-sensitive buildings, information systems, and applications. An accurate determination of an individual's identity supports making sound access control decisions."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "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 is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3:\n\n3.2.5 | The Element | ... 3.2.5 The <xccdf:Value> Element\n\nUse of the <xccdf:source> , <xccdf:complex-value> , and <xccdf:complex-default> elements within the <xccdf:Value> element SHALL NOT be allowed."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Security Assessment?"}, {"role": "assistant", "content": "According to Fiscal Year 2021 Cybersecurity and Privacy Annual Report:\n\n18, NIST published a Federal Register notice that specified the technical requirements for the target cryptographic algorithms and explained the evaluation criteria and a tentative timeline.\nThe standardization process consists of multiple rounds, where, in each round, the field is narrowed to focus on the most promising candidates. In April 2019, NIST announced 56 first-round candidates, and after four months of evaluation, 32 of these candidates proceeded to the second round of evaluation."}], "metadata": {"source": "Fiscal Year 2021 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN):\n\nA Hybrid Satellite Network (HSN), uses independently owned and operated terrestrial and space components to realize a space system that may provide extended global services across diverse missions and connecting points. The HSN architecture typically consists of a combination of independently owned terminals, antennas, satellites, payloads, or other components that communicate across disparate networks. An HSN may interact with government systems and critical infrastructure (as defined by the Department of Homeland Security) to provide services such as satellite-based communications, position, navigation, and timing (PNT), remote sensing, weather monitoring, and imaging. The components within an HSN are likely to have varying levels of trust among different components, requiring frameworks for establishing confidentiality and integrity of individual components while still enabling availability of required shared services. The HSN profile focuses on the complex variety of interfaces, data flows, and interactions with third-party services or component providers involved in modern HSNs. Many of these systems require connections to external partners or entities that are not trusted. Interfacing with untrusted systems requires the individual systems to understand and bound the inherited risk and assure their confidentiality, integrity, and availability. The HSN profile addresses concerns unique to HSN, and the reader is referred to other CSF profiles (such as NISTIR 8401, NISTIR 8323 and others) to address concerns to space system segments or components that are beyond this profile's scope."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "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 Communications Protection?"}, {"role": "assistant", "content": "According to Directions in Security Metrics Research:\n\nPatches and software updates that are intended to repair or improve the security-enforcing mechanisms can lessen the significance of a lagging indicator. Not only does a reset of the baseline system occur with each change, potentially increasing risk [Bre07, Kei08, Lem08, Mar08, Nag08], but an exact picture of the initial baseline becomes obscured and more complicated to track over time (e.g., [Sto08]), making revised assessments impractical. That is, the presumed security posture of the initial baseline is never updated in light of increased understanding, potentially giving a false impression of the actual state. Several recent examples of dramatic shifts in our understanding of vulnerabilities in commonly used technologies, such as the Flash Player-ActionScript virtual machine [Dow08], OpenSSL cryptography [Dou08a, Gar08], MD5 algorithm in Web certificates [Pou08], and DNS protocol implementations [Dou08b], and also the prevalence of zero-day vulnerabilities indicate that with hindsight, unrevised values of lagging indicators could be highly misleading. - [Neu07] Stephan Neuhaus, Thomas Zimmermann, Christian Holler, Andreas Zeller, Predicting Vulnerable Software Components, ACM Conference on Computer and Communications Security (CCS '07), October 29-November 2, 2007, Alexandria, Virginia, http://www.st.cs.uni-sb.de/publications/files/neuhaus-ccs2007.pdf\n- [Ozm06] Andy Ozment, Stuart Schechter, Milk or Wine: Does Software Security Improve with Age?, 15th USENIX Security Symposium, Vancouver, B.C., Canada, July 31-August 4, 2006, http://www.usenix.org/events/sec06/tech/full\\_papers/ozment/ozment.pdf\n- [Pay06] Shirley C."}], "metadata": {"source": "Directions in Security Metrics Research", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1:\n\n-  Risk Management Process - The organization's risk management practices are formally approved and expressed as policy. Organizational cybersecurity practices are regularly updated based on the application of risk management processes to changes in business/mission requirements and a changing threat and technology landscape. -  Integrated Risk Management Program - There is an organization-wide approach to manage cybersecurity risk. Risk-informed policies, processes, and procedures are defined, implemented as intended, and reviewed. Consistent methods are in place to respond effectively to changes in risk. Personnel possess the knowledge and skills to perform their appointed roles and responsibilities. The organization consistently and accurately monitors cybersecurity risk of organizational assets. Senior cybersecurity and non-cybersecurity executives communicate regularly regarding cybersecurity risk. Senior executives ensure consideration of cybersecurity through all lines of operation in the organization. -  External Participation - The organization understands its role, dependencies, and dependents in the larger ecosystem and may contribute to the community's broader understanding of risks. It collaborates with and receives information from other entities regularly that complements internally generated information, and shares information with other entities. The organization is aware of the cyber supply chain risks associated with the products and services it provides and that it uses. Additionally, it usually acts formally upon those risks, including mechanisms such as written agreements to communicate baseline requirements, governance structures (e.g., risk councils), and policy implementation and monitoring."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Computer Security Division 2008 Annual Report:\n\n| Computer Security Division Publications - FY 2008 | 53 55 | | Ways to Engage Our Division and NIST | | | Acknowledgements | 56 |"}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security Strategies for Microservices-based Application Systems provide? (Part 5)"}, {"role": "assistant", "content": "an of T-Mobile for valuable in-line comments and for providing additions to bibliography. Last but not the least, he expresses his thanks to Isabel Van Wyk of G2-Inc for her detailed editorial review.\n## Patent Disclosure Notice\n\nNOTICE: NIST's Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Executive Summary\n\nThe microservices paradigm is being increasingly used for designing and deploying large-scale application systems in both cloud-based and enterprise infrastructures. The resulting application system consists of relatively small, loosely coupled entities or components called microservices that communicate with each other using lightweight communication protocols. Incentives to design and deploy a microservices-based application system include: (a) agility in development due to relatively small and less complex codebases since each one typically implements a single business function; (b) independence among teams in the development process thanks to the loosely coupled nature of microservices; and (c) availability of deployment tools that provide infrastructure services such as authentication, access control, service discovery and communication, and load balancing."}], "metadata": {"source": "Security Strategies for Microservices-based Application Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation:\n\nBGP origin validation relies on a global RPKI system (e.g., certificate authorities, publication repositories, etc.) as the source of trusted information about internet address holders and their route origin authorization statements. Each RIR operates a trusted root certificate authorit y (CA) in the RPKI system and publishes a Certificate Practice Statement [RFC7 382] describing the security and robustness properties of each implementation. Each RPKI CA has integrity and authentication mechanisms for data creation, storage, and transmission. Nevertheless, compromise of the underlying servers and/or registry services is still a potential, if low probability, threat. Making security recommendations for mitigating against such threats is outside of the scope of this document. Transport layer security is key to the integrity of messages communicated in BGP sessions. Making security recommendations for the underlying transport layer is also outside of the scope of this document. | [Mirai2] | 'Dyn Analysis Summary of Friday October 21 Attack,' Dyn Company News, October 26, 2016. https://dyn.com/blog/dyn-analysis-summary-of- friday-october-21-attack/ |\n|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [Murphy] | S. Murphy, 'RPKI Tutorial: Routing Security and RPKI', NANOG on the Road (NOTR), St."}], "metadata": {"source": "Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation", "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 to Cyber Threat Information Sharing:\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\nRather than attempting to establish sharing agreements during an active cyber incident, organizations should plan ahead and have agreements in place before incidents occur. Such advanced planning helps ensure that participating organizations establish trusted relationships and understand their roles, responsibilities, and information handling requirements.\n\nAn organization can use shared threat information in many ways. Some uses are operationally oriented, such as updating enterprise security controls for continuous monitoring with new indicators and configurations to detect the latest attacks and compromises. Threat information may also be used strategically, such as using shared threat information as inputs when planning major changes to an organization's security architecture."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "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 Attribute Considerations for Access Control Systems:\n\nOnce attributes and their allowable values are established, methods for provisioning attributes and appropriate attribute values to subjects and objects within a framework for storing, retrieving, updating, or revoking attributes must also be established. In addition, interfaces and mechanisms must be developed or adopted to enable sharing of these attributes. Finally, to achieve the assurance of attributes, an Attribute Evaluation Scheme, which brings confidence based on the five principal areas of interest, needs to be established:\n\nNIST Special Publication (SP) 800-162, Guide to Attribute Based Access Control (ABAC) Definition and Considerations [1], introduced guidance on access control definitions and considerations for the implementation of access control systems but did not include detailed recommendations on considerations such as the preparation, veracity, security, readiness, and management of attributes. This document aims to provide federal agencies with a guide to attribute considerations with Attribute Evaluation Scheme examples for access control. The Attribute Evaluation Scheme should be determined by an enterprise information system's requirements, and the enterprise information system should validate these requirements to realize the appropriate organizational attribute evaluation scheme capability in line with performance and cost recommendations. Note that this document does not establish a universal attribute scheme that suits all business capabilities and performance requirements; instead, it provides considerations and examples that can be adapted to meet the specific needs of an organization when defining its attribute evaluation scheme. | | Executive Summary....................................................................................................."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n3.4.2 PM-9 |\n| IDENTIFY | Risk Management Strategy (ID."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "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 Access Control?"}, {"role": "assistant", "content": "According to An Industrial Control System Cybersecurity Performance Testbed:\n\nReceptacle for Machining Stations .....................................................................................12 | | 3.2.3.1 | Robot Assembly Table.....................................................................................................12 | Robot Assembly Table.....................................................................................................12 | | 3.2.4 | Emergency Stop Operation.................................................................................................13 | Emergency Stop Operation.................................................................................................13 | | 3.2.5 | Software Architecture.........................................................................................................14 | Software Architecture.........................................................................................................14 | | 3.2.5.1 | Control Layer...................................................................................................................14 | Control Layer...................................................................................................................14 | | 3.2.5.2 | PLC I/O Layer...................................................................................................................15 | PLC I/O Layer...................................................................................................................15 | | 3.2.5.3 | ROS Bags .........................................................................................................................15 | ROS Bags .........................................................................................................................15 | | 3.2.5.4 | ROS versus ROS Industrial...............................................................................................15 | ROS versus ROS Industrial...............................................................................................15 | | 3.2.5.5 | Theory of Operation........................................................................................................15 | Theory of Operation........................................................................................................15 | | 3.2.6 | Final Assembly.....................................................................................................................16 | Final Assembly.....................................................................................................................16 | | 3.3 | Third Enclave Concepts...............................................................................................................16 | Third Enclave Concepts...............................................................................................................16 | | 3.3.1 | Intelligent Transportation System ......................................................................................16 | Intelligent Transportation System ......................................................................................16 | | 3.3.2 | Wide-area Networks with SCADA.......................................................................................16 | Wide-area Networks with SCADA.......................................................................................16 |"}], "metadata": {"source": "An Industrial Control System Cybersecurity Performance Testbed", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Reference Architecture:\n\nDigital forensics is the application of science and technology to the discovery and examination of digital artifacts to establish facts and evidence concerning events and conditions that occur within information systems and networks. For decades, information processing systems have enabled the storage, processing, and transmission of information for public and private organizations and individuals. The maintenance, operation, and protection of these information systems have become paramount concerns since a disruption of sufficient magnitude or specific type could threaten business activities. In addition, the use of these systems in support of criminal activities has been of major concern. Digital forensics has traditionally been used for judicial proceedings and regulatory issues but may also be used for other purposes described below.\n\n- NOTE 1: When this circle is reached, the challenge is neither technical nor non-technical. Fortunately, none of the challenges reach this node as none have this property. This node is included simply for logical completeness of the flowchart, so that every node has both a YES exit path and a NO exit path.\n- NOTE 2: When this circle is reached, the capability is neither technical nor non-technical. There are a few capabilities that reach this node. However, these capabilities do not deal with issues directly related to digital forensics for cloud computing. Rather, they involve controlling physical access to facilities (e.g., using barriers, security patrols, checking physical ID cards.) and mitigating physical threats to facilities (e.g., installing fire suppression equipment).\n\nA person who is an expert in acquiring, preserving, analyzing, and presenting digital evidence from computers and other digital media. This evidence may be related to both computer-based and non-cybercrimes, including security threats, cyber attacks, and other illegal activities."}], "metadata": {"source": "NIST Cloud Computing Forensic Reference Architecture", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Symposium on Federally Funded Research on Cybersecurity of Electric Vehicle Supply Equipment (EVSE):\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": "Symposium on Federally Funded Research on Cybersecurity of Electric Vehicle Supply Equipment (EVSE)", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\n| |\n| 11:00AM - 11:55AM | IR 8259 Rev.\n1 Preliminary Update: Session 1 Activity 1: Identify Expected Customers and Define Expected Use Cases and Activity 2: Research Customer Cybersecurity Needs and Goals | Mike Fagan, NIST |\n| 11:55AM - 1:00 PM | Lunch Break | |\n| 1:00 PM - 1:45PM | Afternoon Keynote Presentation: Leveraging FIDO Alliance cybersecurity standards in support of IR8259 | Brad Goodman (Fast Identity Online Alliance and Dell) |\n| 1:45 PM - 2:45PM | IR 8259 Rev. 1 Preliminary Update: Session 2 Activity 3: Determine How to Address Customer Needs and Goals and Activity 4: Plan for Adequate Support of Customer Needs and Goals | Mike Fagan, NIST |\n| 2:45 PM - 3:00PM | Break | |\n| 3:00 PM - 3:45PM | IR 8259 Rev."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "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 Incident Response?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic:\n\n..................................5 |\n\n## Incident Response and Recovery\n\nThe key focus of the Mayo Clinic's cybersecurity and supply chain incident response plans is the continuation of patient care.\nA dedicated business continuity team within the SCM manages supply chain resiliency events, which are often first identified by other hospitals and health networks that share the supplier. For instance, when the Illinois Environmental Protection Agency shut down the medical supply sterilization company Sterigenics v in February 2019, the Mayo Clinic's business continuity team proactively engaged vendors reliant on Sterigenics to identify alternative sourcing. The business continuity team stores safety reserves of critical supplies to mitigate the impact of supply chain disruptions. While most Mayo Clinic facilities leverage high-efficiency 'just-in-time' operations and supply delivery, these reserves may be deployed to any facility in the network."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8558/final, including related content, potential updates, and document history.\n\nThe team identified that firmware updates are critical to the cybersecurity of a smart teddy bear. Team participants also noted that privacy was also noted as a critical concern. The team envisioned utilizing videos and physical manuals to communicate with customers and users. They developed two manuals: one for parents and another for children, allowing for a more targeted audience approach. The adult manual was detailed and focused on salient tips and direct, easy access to resources. The child manual was designed around the idea that the child could help drive cybersecurity and that the product could help teach good cyber hygiene. For example, the eyes of the bear can glow red when an update is needed, prompting the child to seek help, as the team describes in their mock-up of the story book in Fig. 2."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to CMVP Documentation Requirements_ 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": "CMVP Documentation Requirements_ 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to A Security Perspective on the Web3 Paradigm:\n\n.............................22 |\n| List of Tables |\n| Table 2.\nCurrent web data model vs. Web3 data model.......................................................................6 |"}], "metadata": {"source": "A Security Perspective on the Web3 Paradigm", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case:\n\n## Revision to Include Updates in Cybersecurity Framework Version 1.1\n\nThe Cybersecurity Framework Manufacturing Profile, NISTIR 8183, is scheduled to be revised to include the updates in the Cybersecurity Framework Version 1.1, and will be published as NISTIR 8183, Revision 1.\n\nOnce NISTIR, 8183, Revision 1 has been released, this implementation guide will be revised to include the updates in the Cybersecurity Framework Version 1.1 as well, and will be published as NISTIR 8183A, Revision 1."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Computer Security Division 2006 Annual Report:\n\nTo keep pace with the rate of change in emerging technologies, we conduct a large amount of research in existing and emerging technology areas. Some of the many topics we research include smart card infrastructure and security, wireless and mobile device security, voice over Internet Protocol (IP) security issues, digital forensics tools and methods, access control and authorization management, Internet Protocol security, intrusion detection systems, quantum information system security and quantum cryptography, and vulnerability analysis. Our research helps to fulfill specific needs by the Federal government that would not be easily or reliably filled otherwise.\n\n## Digital Handheld Device Forensics\n\nThe digital forensic community faces a constant challenge to stay on top of the latest technologies that may be used to recover evidence. One such area concerns handheld device forensics. Personal digital assistants (PDAs) and cell phones, including converged PDA/cell phone devices, are commonplace in today's society. They are used by individuals for both personal and professional purposes. Handheld device technologies are evolving rapidly with new products and features being introduced regularly. Rather than just placing calls, cellular devices can allow users to perform additional tasks such as Short Message Service (SMS) messaging, Multi-Media Messaging Service (MMS) messaging, Instant Messaging (IM), electronic mail exchange, Web browsing, Personal Information Management (PIM) maintenance (e.g., address book, task list, and calendar schedule), and even the reading, editing, and production of digital documents. When used over time, these devices tend to accumulate a significant amount of information that may pertain to an incident or crime."}], "metadata": {"source": "Computer Security Division 2006 Annual Report", "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 Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nCHAPTER ONE INTRODUCTION ............................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY .......................................................................................................... 1\n1.2 TARGET AUDIENCE ............................................................................................................................ 4\n1.3 RELATED PUBLICATIONS AND ASSESSMENT PROCESSES ............................................................... 4\n1.4 ORGANIZATION OF THIS PUBLICATION ........................................................................................... 5\nCHAPTER TWO THE FUNDAMENTALS ..................................................................................................... 6\n2.1 ASSESSMENTS WITHIN THE SYSTEM DEVELOPMENT LIFE CYCLE .................................................. 6\n2.2 CONTROL STRUCTURE AND ORGANIZATION .................................................................................. 7\n2.3 BUILDING AN EFFECTIVE ASSURANCE CASE .................................................................................... 8\n2.4 ASSESSMENT PROCEDURES: ASSESSMENT OBJECTS, METHODS AND OBJECTIVES ................... 11\nCHAPTER THREE THE PROCESS ............................................................................................................. 19\n3.1 PREPARE FOR SECURITY AND PRIVACY CONTROL ASSESSMENTS ............................................... 19\n3.2 DEVELOP SECURITY AND PRIVACY ASSESSMENT PLANS .............................................................. 23\n3.3 CONDUCT SECURITY AND PRIVACY CONTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS ....................................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\nType.............................................................98 | | | C.3.5.8 System and Network Monitoring Information Type...............................................100 | | | C.3.5.9 Information Sharing Information Type...................................................................101 | | | APPENDIX D: IMPACT DETERMINATION FOR MISSION-BASED INFORMATION AND INFORMATION SYSTEMS......................................................102 | | | D.2 Homeland Security.............................................................................................................."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "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 Building Secure Microservices-based Applications Using Service-Mesh Architecture:\n\nThe definition and description of microservices-based application, threats, and security strategies for countering those threats are described in NIST SP 800-204, Security Strategies for Microservices-based Application Systems [1]. The purpose of this chapter is to recap and elaborate on the security requirements for this class of application to provide context for how those requirements are met by the functionality of the Service Mesh described in Chapter 3. This facilitates the development of deployment recommendations for Service Mesh components to meet those requirements in Chapter 4."}], "metadata": {"source": "Building Secure Microservices-based Applications Using Service-Mesh Architecture", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC 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 System and Communications Protection?"}, {"role": "assistant", "content": "According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT):\n\n| Figure 3 - Vehicle-to-Vehicle Communications.............................................................10 | | |--------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------| | Figure 4 - V2X Public Key Infrastructure Overview ......................................................11 | | | Figure 5 - Home Lighting Application............................................................................13 | | | Figure 6 - Precision Medicine Research Case | .............................................................16 | | Figure 7 - Diabetes Treatment/Allergen Identification...................................................17 | | | Figure 8 - IoT for the GSA Smart Building....................................................................20 | | | Figure 9 - An Example of a Smart Manufacturing Environment....................................21 | | | Figure 10 - Security Management Plan ........................................................................22 | | | List of Tables | | | Table 2 - IoT Components for Intelligent Buildings.................................................19 | | | Connected ID Networks Table 4 - Status of Cybersecurity Standardization for Several IoT Applications | .......................................................................................32 | | | ..56 | | Table 5 - IoT Key Capabilities Transformations .......................................................62 | | | Table 6 - IT Standards Maturity Model ......................................................................63 | | | Table 7 - Cryptographic Techniques Standards | ......................................................64 | | Table 8 - Cyber Incident Management Standards | ....................................................85 | | Table 9 - Hardware Assurance Standards | ................................................................90 | | Table 10 - Identity and Access Management Standards | .........................................93 | | Table 11 - Information Security Management Systems Standards | ......................101"}], "metadata": {"source": "Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)", "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 Information System Security Best Practices for UOCAVA-Supporting Systems:\n\nclaimed identity of a user or system. Establishing the identity of a user is critical to the security of the system since the authenticated identity forms the basis for The strength of authentication necessary depends on the consequences of an authentication error. As such, users with more privileged levels of access should, in general, be authenticated with a higher level of assurance. For example, three likely classes of users on an IT system supporting UOCAVA voting are system administrator, election officials, and voters. Having insufficient authentication for a system administrator can have a much more negative effect on an election than having insufficient authentication of a particular voter because the system administrator has heightened privileges that allow them to affect the validity of votes from many voters. Identification and authentication in face-to-face environments are quite different than in electronic environments. In most cases, electronic authentication (particularly over the Internet) gives much less assurance than in face-to-face environments. For example, seeing a person who is holding a government-issued photo identity card such as a drivers license or passport gives much more assurance than seeing a copy of the photo identity card that was emailed. It should be noted that face-to-face voting normally employs much less stringent verification on government-issued identification than other environments, such as in aviation security screening. Still, physical interaction with physical identification such as drivers' licenses gives a greater opportunity for better authentication than online systems. In this discussion, the person who is asserting his or her identity is called the claimant and the party trying to assess the authenticity of the identity is the verifier . NIST SP 800-63 Rev."}], "metadata": {"source": "Information System Security Best Practices for UOCAVA-Supporting Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.2.1 Job Classifications... 3.2.1 Job Classifications... 3.2.1 Job Classifications..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Managing Information Security Risk_ Organization, Mission, and Information System View:\n\nOrganizational risk can include many types of risk (e.g., program management risk, investment risk, budgetary risk, legal liability risk, safety risk, inventory risk, supply chain risk, and security risk). Security risk related to the operation and use of information systems is just one of many components of organizational risk that senior leaders/executives address as part of their ongoing risk management responsibilities. Effective risk management requires that organizations operate in highly complex, interconnected environments using state-of-the-art and legacy information systems-systems that organizations depend on to accomplish their missions and to conduct important business-related functions. Leaders must recognize that explicit, well-informed riskbased decisions are necessary in order to balance the benefits gained from the operation and use of these information systems with the risk of the same systems being vehicles through which purposeful attacks, environmental disruptions, or human errors cause mission or business failure. Managing information security risk, like risk management in general, is not an exact science. It brings together the best collective judgments of individuals and groups within organizations responsible for strategic planning, oversight, management, and day-to-day operations-providing both the necessary and sufficient risk response measures to adequately protect the missions and business functions of those organizations. The third component of risk management addresses how organizations respond to risk once that risk is determined based on the results of risk assessments."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "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 Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN) provide?"}, {"role": "assistant", "content": "\n\n## NIST Interagency Report NIST IR 8441\n\n## Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)\n\nJames McCarthy\n\nDan Mamula\n\nJoseph Brule\n\nKarri Meldorf\n\nRory Jennings\n\nJohn Wiltberger\n\nChris Thorpe\n\nJohn Dombrowski\n\nO'Ryan Lattin\n\nSam Sepassi\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8441\n\n\n\n## NIST Interagency Report NIST IR 8441\n\n## Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)\n\nJames McCarthy*\n\nNational Cybersecurity Center of Excellence National Institute of Standards and Technology\n\nDan Mamula Joseph Brule Karri Meldorf Rory Jennings John Wiltberger Chris Thorpe John Dombrowski O'Ryan Lattin Sam Sepassi\n\nThe MITRE Corporation\n\n*Former NIST employee; all work for this publication was done while at NIST. This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8441\n\nSeptember 2023\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cybersecurity Framework Profile for Hybrid Satellite Networks (HSN)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Proxy Validation and Verification for Critical AI Systems_ A Proxy Design Process:\n\n| Table of Contents |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| Executive Summary............................................................................................................................1 |\n| 1. Introduction...................................................................................................................................2 |\n| 2. CAIS Validation and Verification Process -5phases.......................................................................3 |\n| 2.2.1. Physical Operational Environment...............................................................................................5 |\n| 2.2.2. Application Purpose .....................................................................................................................5 |\n| 2.2.3. Operational Characteristics..........................................................................................................6 |\n| 2.2.4. AI/ML Development Algorithms...................................................................................................6 |\n| 2.2.5. AI/ML Development Techniques..................................................................................................7 |\n| 2.2.6. CAIS and Proxy Taxonomy Template............................................................................................7 |\n| References.......................................................................................................................................11 |\n| Appendix A."}], "metadata": {"source": "Proxy Validation and Verification for Critical AI Systems_ A Proxy Design Process", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Analyzing Collusion Threats in the Semiconductor Supply Chain provide? (Part 3)"}, {"role": "assistant", "content": "..................5 |\n| 4. Case Study .....................................................................................................................................8 |\n| 5.\nConclusion and Future Work.........................................................................................................12 |\n| References.......................................................................................................................................13 |\n| List of Figures |\n| Fig. 1. Security challenges in the semiconductor supply chain..............................................................2 |\n| Fig. 2. Methodology for supply chain threat analysis...........................................................................5 |\n| Fig. 3. Threat severity levels for colluding adversaries in the context of hardware Trojan insertion ......6 |\n| Fig. 4. Threat severity levels for colluding adversaries in context of logic obfuscation ........................10 |\n\n## 1. Introduction\n\nThere are numerous security challenges in the semiconductor supply chain. As most chip design companies have become fabless, they rely on offshore foundries for fabrication. This is especially true for the most advanced technology nodes, and the semiconductor supply shock in 2021 has manifested these supply chain security issues. In addition to availability uncertainty, there are many more nuanced security risks in the current semiconductor supply chain, such as IP theft, counterfeiting, Trojan insertion, and reverse engineering. In order to counteract these security risks, many types of solutions have been proposed, ranging from design to test phases of the supply chain."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guide for Mapping Types of Information and Information Systems to Security Categories provide? (Part 3)"}, {"role": "assistant", "content": "dation 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.\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, agencies may wish to closely follow the development of these new documents by NIST. Individuals are also encouraged to review the public draft documents and offer their comments to NIST. All NIST documents mentioned in this publication, other than the ones noted above, are available at http://csrc.nist.gov/publications. COMMENTS MAY BE SUBMITTED TO THE COMPUTER SECURITY DIVISION, INFORMATION TECHNOLOGY LABORATORY, NIST VIA ELECTRONIC MAIL AT SEC-CERT@NIST.GOV OR VIA REGULAR MAIL AT 100 BUREAU DRIVE (MAIL STOP 8930), GAITHERSBURG, MD 20899-8930\n\n## Acknowledgements\n\nThe authors, Kevin Stine, Rich Kissel, and William C. Barker, wish to thank their colleagues, Jim Fahlsing and Jessica Gulick from Science Applications International Corporation (SAIC), who helped update this document, prepare drafts, and review materials. In addition, special thanks are due to our reviewers, Arnold Johnson (NIST), Karen Quigg (Mitre Corporation), and Ruth Bandler (Food and Drug Administration), who greatly contributed to the document's development. A special note of thanks goes to Elizabeth Lennon for her superb technical editing and administrative support."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Computer Security_ Selected Articles:\n\ne users of significant developments in both security' measures and evolving problem categories. - Administer the access control package(s) which run on facilities under control of the DP organization.\nIn this role, the administrator will only permit access to those persons authorized access by those with primary responsibility tor data security. - Take leadership responsibility for determining, by working with the user areas and the Legal Department. the need for a data classification programme. If one is needed, take the lead in developing one that satisfies the potentially diverse needs of the user community. - Develop an Employee Data Security Awareness Programme which will adequately sensitize employees to the importance of their cooperation in the corporate data security program. - Develop educational programmes for user-area management in the use of currently available audit packages for the critical review and evaluation of their data. These users need to be able, whenever possible, to detect data integrity problems before they become any more costly than necessary. This matter is complex and quite beyond the scope of this particular paper - but it is nevertheless very important."}], "metadata": {"source": "Computer Security_ Selected Articles", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity:\n\nThe U.S. standards system differs significantly from the government-driven, centrally-coordinated standards systems common in many other countries. Within the United States, there are hundreds of SDOs, which are overwhelmingly private sector organizations, providing the infrastructure for the preparation of standards documents. USG personnel participate in SDO activities along with representatives from industry, academia, and other organizations and consumers. In many other countries' standards systems, the government plays a larger role in standards development-related activities, which provides those governments the ability to use standards to support domestic industrial and innovation policy, rather than to advance technical solutions in support of public policy goals. While Federal agencies possess certain responsibilities related to standards, such as in their own use of standards or in their development of technical regulations, there is a much greater reliance in the U.S. on the private sector, including companies and industry groups, academic institutions, professional societies, consumer groups, and other interested parties, in standards development. The United States Standards Strategy 8 , elaborated through a private and public sector partnership in 2000, and revised most recently in 2010, outlines the contribution of private-sector led standards development to overall competition and innovation in the U.S. economy and the imperative of public and private sector participation that is a central tenet of the U.S. approach to standardization."}], "metadata": {"source": "Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2008 Annual Report:\n\n| Computer Security Division Publications - FY 2008 | 53 55 | | Ways to Engage Our Division and NIST | | | Acknowledgements | 56 |"}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\ndent [13] information are currently being developed in the IETF Managed Incident Lightweight Exchange (MILE) [14] and the IETF Security Automation and Continuous Monitoring (SACM) [15] working groups.\nA ROLIE repository discovery mechanism [16] and a JSON-based version of ROLIE are also being developed in IETF MILE. Once completed, these solutions will be implemented in the NVD, and can be implemented by vendors to support SCAP content discovery and exchange. - NIST IR 8085: In support of the transition from CPE to SWID, an automated method is needed to support the generation of a CPE Name from a SWID tag to support legacy SCAP v1 tools. Draft NISTIR 8085 [17] is a start to support generation of CPE names from SWIDs, but more work is needed to complete this specification."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out:\n\nThe Contractor shall review network security, evaluating its confidentiality, integrity, and availability. This review shall include, as applicable, access control, authentication, security administration, type and security of network media, security of file and print servers, encryption, interfaces between network and operating system/application software security modules, and conformance to networking standards.\n\nA security plan prepared under OMB Bulletin 90-08 should be an abstract of the detailed security plan for the system. If a detailed security plan does not exist, the OMB Bulletin 90-08 plan can be a starting point. The detailed plan will contain significantly more information in such areas as risk analysis, contingency planning, backup procedures, personnel screening and selection, password management, user identification and authentication, and audit and variance detection.\n\nThe second area measures the impact of a hardware or software product designed to perform a direct computer security function. Examples of this include a virus scanning package, a PC-based access control package, a mainframe access control system, an accounting add-on to an operating system, an encryption device, or a smart card-based identification and authentication system."}], "metadata": {"source": "Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Information Security Handbook_ A Guide for Managers:\n\n| 1. Introduction .................................................................................................... | 1. Introduction .................................................................................................... | 1. Introduction .................................................................................................... | 1. Introduction ...................................................................................................."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines on PDA Forensics:\n\nLinux offers comprehensive support for security that has been part of the operating system from its onset. Features include user identification and authentication, access control on files and directories based on owner (user/group/all), logging of security-relevant activities, and various levels of network encryption (Point-to-Point Tunneling Protocol (PPTP), Internet Protocol Security (IPsec), Secure Shell (SSH), etc.). Processes running under Linux on the same machine are also protected from interfering with one another [Ket00]. Linux operating systems tailored for PDAs have on occasion been found to contain security vulnerabilities in design and implementation that affect system security. For example, the screen-locking passcode on the Zaurus that provides user authentication, created the same random value (i.e., salt value 15 ) every time the passcode was set. This oversight weakened security by allowing\n\n- „ Identification - Recognize and determine the type of incident. - „ Preparation - Prepare tools, techniques, search warrants, authorizations, and management approval. - „ Approach Strategy - Maximize untainted evidence collection while minimizing the impact upon the victim. - „ Preservation - Isolate, secure, and preserve the state of physical and digital evidence. - „ Collection - Record the physical scene and duplicate digital evidence. - „ Examination - Search for evidence relating to the suspected crime. - „ Analysis - Determine significance, reconstruct fragments of data, and draw conclusions based on the evidence found. The Analysis phase may go through numerous iterations until a theory has been supported. - „ Presentation - Summarize and provide an explanation of conclusions."}], "metadata": {"source": "Guidelines on PDA Forensics", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1:\n\n3.4.2 ISO/IEC 27001:2013 Clause 6. 3.4.2 ISO/IEC 27001:2013 A."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1", "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 Planning?"}, {"role": "assistant", "content": "According to Guide for Security-Focused Configuration Management of Information Systems:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of 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 Planning?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 1_ Overview:\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 new publications by NIST.\n\nAs a corollary to the assumption that an initial A&A was conducted consistent with SP 800-37 and related guidance, there is an assumption that the system(s) being assessed have the normal complement of security documentation, including the system security plan, the initial (or most current) security assessment report, and supporting documents such as the system contingency plan.\n\nAwareness of the results to be produced facilitates better security engineering, by allowing security control designers to look at controls as parts of a system designed to achieve an overall purpose, allowing them to better control design and planning decisions."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "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 Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\n............................................................................... | Executive Summary.....................................................................................................\n|\n|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 |\n| 1.1 | History of TLS................................................................................................. | 1 |\n| 1.2 | Scope.............................................................................................................."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to 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 Services Acquisition?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test 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. The authors (David Cooper, Hildegard Ferraiolo and Ramaswamy Chandramouli of NIST; Nabil Ghadiali of the National Gallery of Art; and Jason Mohler and Steven Brady of Electrosoft Services, Inc.), wish to thank their colleagues who reviewed drafts of this document and contributed to its development."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Reference Architecture:\n\ncontributed significantly to researching this topic and to generating the data included in this publication, which constitutes the foundation of NIST's Cloud Computing Forensic Reference Architecture.\nThe authors thank Richard Lee of Citizens Financial Group, who served as a reviewer; Rodrigo Sardinas of Auburn University; Pw Carey of Grapevine Solutions; Richard Austin, formerly of HewlettPackard Enterprise; Dr. Ken Stavinoha, formerly with Cisco Systems; and Otto Scot Reemelin, who was with Ipro Tech during this work, for contributing to the data collection, analysis, and review. The authors would also like to thank Josiah Dykstra of the National Security Agency, Kenneth R. Zatyko of Buffalo Block Chain, and independent expert Keyun Ruan for their contributions during the early stages of this research. Finally, the authors wish to thank their peers who continuously provided feedback during the research and development stages of this document."}], "metadata": {"source": "NIST Cloud Computing Forensic Reference Architecture", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions:\n\n| Key derivation function. |\n| KECCAK | The family of all sponge functions with a KECCAK- f permutation as the underlying function and multi-rate padding as the padding rule.\nKECCAK was originally specified in [8]. |\n| lane | For a state array of a KECCAK- p permutation with width b , a sub-array of b /25 bits with constant x and y coordinates. |\n| message | A bit string of any length that is the input to a SHA-3 function. |\n| multi-rate padding | The padding rule pad10*1, whose output is a 1 , followed by a (possibly empty) string of 0 s, followed by a 1 . |\n| NIST | National Institute of Standards and Technology. |\n| plane | For a state array of a KECCAK- p permutation with width b , a sub-array of b /5 bits with a constant y coordinate. |\n| rate | In the sponge construction, the number of input bits processed or output bits generated per invocation of the underlying function. |\n| round | The sequence of step mappings that is iterated in the calculation of a KECCAK- p permutation. |\n| round constant | For each round of a KECCAK- p permutation, a lane value that is determined by the round index. The round constant is the second input to the ι step mapping. |\n| round index | The value of the integer index for the rounds of a KECCAK- p permutation. |\n| row | For a state array, a sub-array of five bits with constant y and z coordinates. |\n| SHA-3 | Secure Hash Algorithm-3. |\n| SHAKE | Secure Hash Algorithm KECCAK. |\n| sheet | For a state array of a KECCAK- p permutation with width b , a sub-array of b /5 bits with a constant x coordinate. |\n| slice | For a state array, a sub-array of 25 bits with a constant z coordinate. |"}], "metadata": {"source": "SHA-3 Standard_ Permutation-Based 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 Media Protection?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe resulting tailored baseline set of security controls and the supporting rationale for the selection decisions (including any information system use restrictions required by organizations) are documented in system security plans. Documenting significant risk management decisions in the security control selection process is imperative so that authorizing officials have access to necessary information to make informed authorization decisions for organizational information systems, as demonstrated in Figure 3."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Non-Fungible Token Security:\n\nIf the smart contract contains coding errors, there may be a vulnerability that enables an attacker to steal tokens. An evaluation of possible vulnerabilities in NFT contracts is available from [30]. The attacker would then likely sell the tokens quickly to obtain cryptocurrency because after launching the attack, their approach would be publicly visible on the blockchain. Others could then launch the same attack, or the contract manager could use the same vulnerability to restore tokens to their owners. If the contract manager can regain control of the smart contract, tokens could be restored. However, the attacker would still have the funds obtained through illegal token sales and the sold tokens would each have two owners (the original owners to whom the tokens are restored and the subsequent purchasers that unwittingly bought the stolen tokens).\n\nAn NFT is expected to have the property of being unchanging or immutable. NFT smart contracts enforce this in their code. However, a vulnerability in the smart contract could enable a malicious entity to change NFT data records.\n\n20. If the smart contract code contains a vulnerability, the data records could be changed by a malicious actor.\n21. Blockchains are occasionally changed through participant consensus or have their chains split into distinct and different versions when consensus is not reached on resolving a major issue.\n22. A blockchain split will result in the duplication of NFT contracts, which in turn results in NFT owners having the same NFTs on two blockchains. They could sell one and keep the other, causing significant issues for NFTs that convey ownership rights over their linked asset."}], "metadata": {"source": "Non-Fungible Token Security", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Incident Response?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Guide to Secure Web Services:\n\n3.2.2 | Laws of Identity... 3.2.2 Laws of Identity\n\nIn May 2005, Kim Cameron, Identity and Access Architect at Microsoft, authored The Laws of Identity 30 based on his research into the requirements for a unified identity metasystem , a system of identity systems that exposes a unified interface for disparate underlying identity technologies. 3.2.2 WS-Federation and WS-Trust\n\nWS-Federation and WS-Trust were developed by IBM, Microsoft, RSA, Verisign, BEA, and several other vendors to create an identity federation system based on extensions to WS-Security that uses the core Web services protocols: SOAP and WSDL."}], "metadata": {"source": "Guide to Secure Web Services", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to A Roadmap for Successful Regional Alliances and Multistakeholder Partnerships to Build the Cybersecurity Workforce:\n\nPatty Buddelmeyer Southwestern Ohio Council for Higher Education Dayton, OH\n\nIn September 2016, the National Initiative for Cybersecurity Education, led by the National Institute of Standards and Technology in the U.S. Department of Commerce, awarded funding for five pilot programs for Regional Alliances and Multistakeholder Partnerships to Stimulate (RAMPS) Cybersecurity Education and Workforce Development. The document that follows provides a summary of the five pilot programs and outlines a roadmap for building similar programs based on the best practices found and lessons learned.\n\nalliance; collaboration; cybersecurity; education; partnership; RAMPS; stakeholder; workforce."}], "metadata": {"source": "A Roadmap for Successful Regional Alliances and Multistakeholder Partnerships to Build the Cybersecurity Workforce", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992:\n\n- Establish security responsibility (e.g. security officers) (Priority A).\n- -Develop and maintain site security policy and procedures, including a policy for handling security incidents.\n- Support comprehensive security education programs for users.\n- -Establish Forum of Incident Response Security Teams (FIRST) point of contacts.\n\nWe have security policy that we are willing to share with others; it has already been shared it with NCSA. We have an incident response team (such that it is) of about three people. We maintain a contact in the local FBI office so they will not be taken by surprise if we call them for help on a computer security problem.\n\nSTEINAUER; The Forum of Incident Response Security Teams (FIRST) is a cooperative effort involving a number of organizations. The concept of FIRST arose as the result of the 'Internet Worm' incident, along with a number of things that were going on in that period of time. It was clear that the basic nature of security threats had substantially changed and there were new requirements."}], "metadata": {"source": "Report of the NSF_NIST Workshop on NSFNET_NREN Security, July 6-7, 1992", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Computer Security Division 2007 Annual Report:\n\n), and security planning. Together, these tenets will revolutionize healthcare, making it more consumercentric, and will improve both the quality and the efficiency of healthcare in the United States.\nOne of the critical components of these tenets is the assurance of privacy of health-related information as well as assuring the confidentiality and integrity of all health information technology (HealthIT) data and maintaining the availability to HealthIT whenever it is needed. CSD is intricately involved in assisting healthcare providers in this effort."}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\n............................................................................. | Introduction............................................................................................................\n| 1 |\n| | 1.1 Purpose.....................................................................................................................................1 | 1.1 Purpose.....................................................................................................................................1 | |\n| | 1.2 Scope........................................................................................................................................2 | 1.2 Scope........................................................................................................................................2 | |\n| | 1.3 Audience ...................................................................................................................................2 | 1.3 Audience ...................................................................................................................................2 | |\n| | 1.4 Document Structure ..................................................................................................................2 | 1.4 Document Structure ..................................................................................................................2 | |\n| 2 | Consideration Elements........................................................................................ | Consideration Elements........................................................................................ | 4 |\n| 3 | Attribute Considerations....................................................................................... | Attribute Considerations......................................................................................."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines on Active Content and Mobile Code provide? (Part 2)"}, {"role": "assistant", "content": "is 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.\nNational Institute of Standards and Technology Special Publication 800-28 Version 2 Natl. Inst. Stand. Technol. Spec. Publ. 800-28v2, 62 pages (Mar. 2008)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## Acknowledgements\n\nThe authors, Wayne A. Jansen and Karen Scarfone of the National Institute of Standards and Technology (NIST) and Theodore Winograd of Booz Allen Hamilton, wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content, particularly Tim Grance and Anoop Singhal of NIST, Edward Tracy of Booz Allen Hamilton, and Kurt Dillard."}], "metadata": {"source": "Guidelines on Active Content and Mobile Code", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\n| 1.4 | Terminology | 1-7 |\n| | 1.5 | Document Organization | 1-7 |\n| 2.\n| Rationale | Rationale | 2-1 |\n| | 2.1 | Intended Method of Use | 2-1 |\n| | 2.2 | Environmental Assumptions | 2-1 |\n| | 2.3 | Expected Threats | 2-2 |\n| | 2.4 | Security Features and Assurances | 2-2 |\n| | | 2.4.1 Identification and Authentication | 2-3 |\n| | 2.4.2 | Access Control | 2-3 |\n| | 2.4.3 | Audit | 2-3 |\n| | 2.4.4 | System Integrity | 2-4 |\n| | 2.4.5 | Data Integrity | 2-4 |\n| | 2.4.6 | Reliability of Service | 2-4 |\n| | 2.4.7 | Product Development Assurance | 2-4 |\n| | 2.4.8 | Product Documentation Assurance | 2-5 |"}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective:\n\nSystem Security Engineering standards describe planning and design activities to meet security specifications or requirements for the purpose of reducing system susceptibility to threats, increasing system resilience, and enforcing organizational security policy. A comprehensive system security engineering effort: includes a combination of technical and nontechnical activities; ensures all relevant stakeholders are included in security requirements definition activities; ensures that security requirements are planned, designed, and implemented into a system during all phases of its lifecycle; assesses and understands susceptibility to threats in the projected or actual environment of operation; identifies and assesses vulnerabilities in the system and its environment of operation; identifies, specifies, designs, and develops protective measures to address system vulnerabilities; evaluates/assesses protective measures to ascertain their suitability, effectiveness and degree to which they can be expected to reduce mission/business risk; provides assurance evidence to substantiate the trustworthiness of protective measures; identifies quantifies, and evaluates the costs and benefits of protective measures to inform engineering trade-off and risk response decisions; and leverages multiple security focus areas to ensure that protective measures are appropriate, effective in combination, and interact properly with other system capabilities. Emergency Management First responders use private, land mobile radio systems for their mission critical voice communications. These networks are designed and built on a set of standards and user requirements that address critical operational concerns, including user authentication, security and reliability. With emergence of broadband applications and services, first responders are beginning to incorporate broadband data applications into their day-to-day operations."}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "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 Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity” provide? (Part 5)"}, {"role": "assistant", "content": ".................................16 |\n| | B.\nList of Symbols, Abbreviations, and | |\n| Appendix | Acronyms...........................................20 | |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Workshop Agenda..........................................................................................................2 | Table 1. Workshop Agenda..........................................................................................................2 | Table 1. Workshop Agenda..........................................................................................................2 |\n\n## Introduction\n\nOn June 22, 2022, the National Institute of Standards and Technology (NIST) conducted a virtual workshop entitled Building on the NIST Foundations: Next Steps in IoT Cybersecurity ."}], "metadata": {"source": "Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to An Introduction to Information Security:\n\n| | 6.3 Implement ....................................................................................................... 37 |\n|--------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|\n| 6.4 Assess ............................................................................................................ | 37 |\n| 6.5 Authorize......................................................................................................... | 37 |\n| 6.6 Monitor............................................................................................................ | 37 |\n| 7 Assurance.............................................................................................................38 | |\n| 7.1 Authorization ..................................................................................................."}], "metadata": {"source": "An Introduction to Information Security", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\nto comply with applicable provisions of NMI 2410.7 and this Handbook. - (6) Review and concur on exceptions from implementing specific requirements of this Handbook. - e. Other Headquarters Offices .\nOther HQ offices that play an integral role include the:\n- (1) Inspector General, which has independent audit and criminal investigation responsibilities. - (2) NASA Security Office, which has traditional security responsibilities in the areas of personnel security, physical security, and national (including defense-related) security documents and operations control. - (3) Office of Space Operations, which has agencywide responsibilities for telecommunications security. - (4) Office of Procurement, which has responsibilities for ensuring that appropriate functional security requirements are included in acquisitions for automated information products and services. - (5) Management Operations Office, which has responsibilities for the NASA Internal Controls Program\n- (6) Office of Safety, Reliability, Maintainability, and Quality Assurance, which has responsibilities related to automated information resources supporting manned space flight."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "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 Security Assessment?"}, {"role": "assistant", "content": "According to Guidelines for Evaluating Differential Privacy Guarantees:\n\n## Toward Standardization, Certification, and Evaluation\n\nThe pyramid and accompanying evaluation processes are not designed for setting the parameters of a differential privacy guarantee, though they can support it. Planning a differentially private data release or designing a differentially private system requires eliciting requirements from various stakeholders-for privacy, utility, usability, trust models, and more-then setting the parameters of the differential privacy guarantee to meet these requirements. Since differential privacy involves tradeoffs between the elements of the guarantee, it is often impossible to meet all of the requirements simultaneously, so arriving at a final design requires iterative negotiation involving all of the stakeholders.\n\nThe most precise approaches for interpreting and comparing differential privacy guarantees are based on hypothesis testing [23, 24] or interpretation via Bayesian or frequentist semantics [14]. These approaches allow direct, precise interpretation of the privacy guarantee. For example, the formal definition of pure ε -differential privacy (Definition 1) can be viewed as bounding the error rates in a hypothesis test over the output of a differentially private mechanism:"}], "metadata": {"source": "Guidelines for Evaluating Differential Privacy Guarantees", "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 The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\n'We have one annual course, and we've bundled a lot of training requirements in this one course. It's security awareness, privacy, incident response, rules of behavior, all these things in one course.' (S06)\n\n'Logistics and event planning are key KSA [knowledge, skills, and abilities] areas.' (Q56)"}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to General Server Security:\n\n| Introduction | ......................................................................................................................1-1 | | | | 1.1 | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope .................................................................................................1-1 | | | | 1.3 | Audience..................................................................................................................1-2 | | | | 1.4 | Document Structure.................................................................................................1-2 | | | 2."}], "metadata": {"source": "Guide to General Server 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 does CMMC Level 2 require for Personnel Security?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n| Table 1. Security Requirement Families .......................................................................................................4 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. Security Control Tailoring Criteria.................................................................................................93 |\n| Table 3. Access Control (AC) .......................................................................................................................93 |\n| Table 4. Awareness and Training (AT).........................................................................................................94 |\n| Table 5. Audit and Accountability (AU).......................................................................................................95 |\n| Table 6. Assessment, Authorization, and Monitoring (CA).........................................................................95 |\n| Table 7. Configuration Management (CM).................................................................................................96 |\n| Table 8. Contingency Planning (CP) ............................................................................................................96 |\n| Table 9. Identification and Authentication (IA) ..........................................................................................97 |\n| Table 10. Incident Response (IR).................................................................................................................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines on Firewalls and Firewall Policy:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guidelines on Firewalls and Firewall Policy", "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 Guide to Operational Technology (OT) Security:\n\n4.2.1. Supply Chain Risk Management .............................................................................54\n\n6.1.5. Supply Chain Risk Management (ID.SC) .................................................................95\n\nD.2.14. NIST Supply Chain Traceability for Agri-Food Manufacturing ............................ 200"}], "metadata": {"source": "Guide to Operational Technology (OT) Security", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to 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 guidance does NIST provide for CMMC Level 1?"}, {"role": "assistant", "content": "According to A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data:\n\n## NISTIR 8221\n\n## A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data\n\nRamaswamy Chandramouli Anoop Singhal Duminda Wijesekera Changwei Liu\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8221\n\n\n\n## NISTIR 8221\n\n## A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data\n\nRamaswamy Chandramouli Anoop Singhal Duminda Wijesekera Computer Security Division Information Technology Laboratory\n\nChangwei Liu George Mason University Fairfax, VA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8221\n\nJune 2019\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\n## National Institute of Standards and Technology Interagency or Internal Report 8221 35 pages (June 2019)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8221\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": "A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI:\n\n3.1.1\nAPTL: 100342\n\nMindcraft, Inc. 3.1.1\nAPTL: 100342\n\nMindcraft, Inc."}], "metadata": {"source": "Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThe National Institute of Standards and Technology (NIST) Information Technology Laboratory (ITL) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology (IT). ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the costeffective security of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information systems security and privacy and its collaborative activities with industry, government, and academic organizations. All information systems process, store, or transmit some type of information. For example, information about the temperature in a remote facility collected and transmitted by a sensor to a monitoring station, location coordinates transmitted by radio to a controller on a weapons system, photographic images transmitted by a remote camera (land/satellite-based) to a server, or health IT devices transmitting patient information via a hospital network, require protection. This information can be protected by: categorizing the information to determine the impact of loss; assessing whether the processing of the information could impact individuals' privacy; and selecting and implementing controls that are applicable to the IT resources in use. Therefore, cloud-based systems, industrial/process control systems, weapons systems, cyber-physical systems, applications, IoT devices, or mobile devices/systems, do not require a separate risk management process but rather a tailored set of controls and specific implementation details determined by applying the existing RMF process."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop provide?"}, {"role": "assistant", "content": "## NISTIR 8322\n\n## Workshop Summary Report for 'Building the Federal Profile for IoT Device Cybersecurity' Virtual Workshop\n\nKaterina N. Megas Michael Fagan David Lemire\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8322\n\n\n\n## NISTIR 8322\n\n## Workshop Summary Report for 'Building the Federal Profile for IoT Device Cybersecurity' Virtual Workshop\n\nKaterina N. Megas Michael Fagan Applied Cybersecurity Division Information Technology Laboratory\n\nDavid Lemire Huntington Ingalls Industries Annapolis Junction, MD\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8322\n\nJanuary 2021\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 8322 30 pages (January 2021)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8322\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": "Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation:\n\nth industry, government, and academic organizations. | [RouteLeak1] | K. Sriram (Ed.) and A. Azimov (Ed.), 'Methods for Detection and Mitigation of BGP Route Leaks', IETF Internet Draft, July 2019.\nhttps://datatracker.ietf.org/doc/draft-ietf-grow-route-leak-detection- mitigation/ |\n|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [RouteLeak2] | A. Azimov, E. Bogomazov, R. Bush, K. Patel, and K. Sriram, \"Route Leak Prevention using Roles in Update and Open Messages\", IETF Internet Draft, July 2019. https://datatracker.ietf.org/doc/draft-ietf-idr- bgp-open-policy/ |\n| [RouteLeak3] | K. Sriram (Ed.), 'Design Discussion of Route Leaks Solution Methods', IETF Internet Draft, August 2019. https://datatracker.ietf.org/doc/draft- sriram-idr-route-leak-solution-discussion/ |\n| [Routinator] | Routinator: NLNetLabs' RPKI validator. https://nlnetlabs.nl/projects/rpki/routinator/ |\n| [Rsync] | Wiki page on the Rsync protocol."}], "metadata": {"source": "Resilient Interdomain Traffic Exchange_ BGP Security and DDoS Mitigation", "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 Minimum Security Requirements for Multi-User Operating Systems:\n\n| 1.4 | Terminology | 1-7 |\n| | 1.5 | Document Organization | 1-7 |\n| 2.\n| Rationale | Rationale | 2-1 |\n| | 2.1 | Intended Method of Use | 2-1 |\n| | 2.2 | Environmental Assumptions | 2-1 |\n| | 2.3 | Expected Threats | 2-2 |\n| | 2.4 | Security Features and Assurances | 2-2 |\n| | | 2.4.1 Identification and Authentication | 2-3 |\n| | 2.4.2 | Access Control | 2-3 |\n| | 2.4.3 | Audit | 2-3 |\n| | 2.4.4 | System Integrity | 2-4 |\n| | 2.4.5 | Data Integrity | 2-4 |\n| | 2.4.6 | Reliability of Service | 2-4 |\n| | 2.4.7 | Product Development Assurance | 2-4 |\n| | 2.4.8 | Product Documentation Assurance | 2-5 |"}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\nManager, Computer Security Planning"}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Applications Using Approved Hash Algorithms:\n\nThe author, Quynh Dang of the National Institute of Standards and Technology (NIST) gratefully appreciates the contributions and comments from Elaine Barker, William E. Burr, Shu-jen Chang, Lily Chen, Donna F. Dodson, Morris Dworkin, John Kelsey, Ray Perlner, W. Timothy Polk and Andrew Regenscheid. The author also appreciates comments from Daniel Brown, Hugo Krawczyk, Praveen Gauravaram and Richard Davis during the development of this Recommendation."}], "metadata": {"source": "Recommendation for Applications Using Approved Hash Algorithms", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.4 (NIST 3.4.4)?"}, {"role": "assistant", "content": "According to Guidelines for Evaluating Differential Privacy Guarantees:\n\n3.4.4. 3.4.4."}], "metadata": {"source": "Guidelines for Evaluating Differential Privacy Guarantees", "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 System and Communications Protection?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | |---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | | Introduction | ......................................................................................................................1-1 | | | | 1.1 | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope | | | | 1.3 | .................................................................................................1-1 Audience..................................................................................................................1-1 | | | | 1.4 | Document Structure.................................................................................................1-1 | | | | 1.5 | How to Navigate This Document .............................................................................1-2 | | | | Overview of Wireless Networking | ..................................................................................2-1 | | | | 2.1 | History of Wireless Networking Standards...............................................................2-1 | | | | | 2.1.1 IEEE 802.11 Standards................................................................................2-1 | | | | | 2.1.2 Wi-Fi Alliance Certification............................................................................2-2 | | | | | 2.1.3 Other Wireless Standards | ............................................................................2-3 | | | 2.2 | IEEE 802.11 Network Components and Architectural Models.................................2-4 | | | | | 2.2.1 Ad Hoc Mode................................................................................................2-4 | | | | | 2.2.2 Infrastructure Mode ......................................................................................2-6 | | | | 2.3 | Summary..................................................................................................................2-6 | | | | Overview | of IEEE 802.11 Security ..................................................................................3-1 | | | | 3.1 | WLAN Security Concerns ........................................................................................3-1 | | | | 3.2 | History of Pre-RSN IEEE 802.11 Security ...............................................................3-2 | | | | | 3.2.1 Access Control and Authentication...............................................................3-2 | | | | | 3.2.2"}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance:\n\naccreditation; assurances; authentication; authorization; availability; backup; certification; compromise; confidentiality; cryptanalysis; cryptographic key; cryptographic module; digital signature; key management; key management policy; key recovery; private key; public key; public key infrastructure; security plan; trust anchor; validation. 1. Government systems shall be configured so that approved algorithms (e.g., AES) shall be used [RFC 3962], and DES shall not be used [RFC 6649]. 2. An approved MAC checksum (e.g., HMAC-SHA1 or HMAC-SHA256-128) shall be installed and used in all implementations for data integrity purposes (see [RFC 3962] and the IETF Informational Draft, AES Encryption with HMAC-SHA2 for Kerberos 5 , at: http://tools.ietf.org/html/draft-ietf-kitten-aes-cts-hmac-sha2-04). 3. The AS, TGS, TSs, and clients shall use strong access control mechanisms 30 (physical and logical) for protecting and updating keys. 4. Kerberos version 5 permits the use of smart cards or tokens (e.g., FIPS 201 Personal Identity Verification cards [FIPS 201]) to store a user's password. Passwords stored on tokens shall be randomly generated; therefore, when tokens are used, a means of generating random passwords by a NIST-approved random number generation function ([SP 800-90A], [SP 800-90B], [SP 80090C]), and securely writing them on the token shall be used. When tokens are used, manual entry of passwords shall not be permitted except to authenticate the user to the token. 5. Kerberos with public key-based user authentication and key establishment can provide stronger security than password-based keys and should be installed where PKI mechanisms are available and the software has the capability. See [RFC 4556] for further information. 6. TLS should be used when the system supports it, see Section 4 for guidelines on using TLS. 7. If user passwords are generated by the system, the system shall generate strong passwords [SP 800-118]."}], "metadata": {"source": "Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\nauthentication; FIPS 201; identity credential; logical access control; on-card biometric comparison; Personal Identity Verification (PIV); physical access control; smart cards; secure messaging. 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. Homeland Security Presidential Directive-12 (HSPD-12) called for the adoption of a common identification standard to govern the interoperable use of identity credentials to allow physical and logical access to federally controlled facilities and information systems. In response, Federal Information Processing Standard (FIPS) 201 [FIPS201], Personal Identity Verification (PIV) of Federal Employees and Contractors , was developed to define reliable, government-wide identity credentials for use in applications such as access to federally controlled facilities and information systems. FIPS 201 supports multiple types of authenticators, including authenticators on smart cards (also known as PIV Cards) and derived PIV credential authenticators in various other form factors. This publication contains technical specifications to interface with PIV Cards to retrieve and use identity credentials."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "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 Computer Security Division 2003 Annual Report:\n\nSystem security accreditation is the official management decision to authorize operation of an information system. This authorization, given by a senior agency official, is applicable to a particular environment of operation, and explicitly accepts the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, remaining after the implementation of an agreed upon set of security controls. By accrediting an information system, the agency official is not only responsible for the security of the system but is also accountable for adverse impacts to the agency if a breach of security occurs. Security accreditation, which is required under OMB Circular A-130, provides a form of quality control and challenges managers and technical staff at all levels to implement the most effective security controls and techniques, given technical constraints, operational constraints, cost and schedule constraints, and mission requirements. In addition to risk assessments and security plans, security evaluation also plays an important role in the security accreditation process. It is essential that agency officials have the most complete, accurate, and trustworthy information possible on the security status of their information systems in order to make credible, riskbased decisions on whether to authorize operation of those systems. This information and supporting evidence for system authorization is often developed during a detailed security review of the information system, typically referred to as security certification. Security certification is the comprehensive evaluation of the management, operational, and technical security controls in an information system."}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "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 The NIST Cybersecurity Framework (CSF) 2.0 provide? (Part 2)"}, {"role": "assistant", "content": "to build and host additional resources to help organizations implement the CSF, including Quick Start Guides and Community Profiles. All resources are made publicly available on the NIST CSF website.\nSuggestions for additional resources to reference on the NIST CSF website can always be shared with NIST at cyberframework@nist.gov. ## Note to Readers\n\nUnless otherwise noted, documents cited, referenced, or excerpted in this publication are not wholly incorporated into this publication. Before version 2.0, the Cybersecurity Framework was called the 'Framework for Improving Critical Infrastructure Cybersecurity.' This title is not used for CSF 2.0. ## Acknowledgments\n\nThe CSF is the result of a multi-year collaborative effort across industry, academia, and government in the United States and around the world. NIST acknowledges and thanks all of those who have contributed to this revised CSF. Information on the CSF development process can be found on the NIST CSF website. Lessons learned about the use of the CSF can always be shared with NIST at cyberframework@nist.gov. | Table of Contents |\n|---------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Cybersecurity Framework (CSF) Overview.......................................................................................1 |\n| 2. Introduction to the CSF Core...........................................................................................................3 |\n| 3. Introduction to CSF Profiles and Tiers .............................................................................................6 |\n| 4. Introduction to Online Resources That Supplement the CSF ............................................................9 |\n| 5."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Computer Security Division 2006 Annual Report:\n\non and information systems using a standardized, risk-based approach - Developed FIPS 200, Minimum Security Requirements for Federal Information and Information Systems (issued March 2006).\n- Define minimum information security requirements (management, operational, and technical security controls) for information and information systems in each such category - Developed SP 800-53, Recommended Security Controls for Federal Information Systems (revision 1 issued December 2006). - Identify methods for assessing effectiveness of security requirements - SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems (second public draft issued April 2006). - B ring the security planning process up to date with key standards and guidelines developed by NIST - SP 800-18 Revision 1, Guide for Developing Security Plans for Federal Information Systems (issued February 2006). - Provide assistance to Agencies and private sector - Conduct ongoing, substantial reimbursable and non-reimbursable assistance support, including many outreach efforts such as the Federal Information Systems Security Educators' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSM Forum), the Small Business Corner, and the Program Review for Information Security Management Assistance (PRISMA). - Evaluate security policies and technologies from the private sector and national security systems for potential Federal agency use - Host a growing repository of Federal agency security practices, public/private security practices, and security configuration checklists for IT products. In conjunction with the Government of Canada's Communications Security Establishment, CSD leads the Cryptographic Module Validation Program (CMVP). The Common Criteria Evaluation and Validation Scheme (CCEVS) and CMVP facilitate security testing of IT products usable by the Federal government."}], "metadata": {"source": "Computer Security Division 2006 Annual Report", "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 Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nSP 800-53 Revision 4 has been updated to reflect the evolving technology and threat space. Example areas include issues particular to mobile and cloud computing; insider threats; applications security; supply chain risks; advanced persistent threat; and trustworthiness, assurance, and resilience of information systems. The revision also contains a new appendix of privacy controls, and related implementation guidance (Appendix J), based on the Fair Information Practice Principles (FIPPs), a widely accepted framework of defining principles to be used in the evaluation and consideration of systems, processes, or programs that affect individual privacy. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security . ISO/IEC 27001 applies to all types of organizations and specifies requirements for establishing, implementing, operating, monitoring, reviewing, maintaining, and improving a documented information security management system (ISMS) within the context of business risks. ISO/IEC 15408 (also known as the Common Criteria) provides functionality and assurance requirements for developers of information systems and information system components (i.e., information technology products)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Introduction to Cybersecurity for Commercial Satellite Operations:\n\n| Functions | Subcategories | Informative | Reference |\n|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|------------------------------------------------------------------------------------------------|\n| | | SP 800-53, Rev. 4 | SP 800-53, Rev. 5 |\n| | PR.PT-4: Communications and control networks are protected. | SC-32, AC-4, AC-17, SC-7 | AC-12, AC-17, CP-8, SC-5, SC-7, SC-10, SC-20, SC-21, SC-22, SC-23, SC-31, SC- 37, SC-38, SC-47 |\n| | PR.PT-5: Mechanisms (e.g., fail- safe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations. | PL-8, SC-6 | PE-11, PL-8, SC-6 |\n| Detect | DE.AE-3: Event data are collected and correlated from multiple sources and sensors. | AU-6, CA-7, IR- 4, IR-5, IR-8, SI- 4 | AU-6, CA-7, IR-4, IR-5, IR-8, SI-4 |\n| | DE.CM-1: The network is monitored to detect potential cybersecurity events. | SC-5 | AU-12, CA-7, CM-3, SC-5, SC-7, SI-4 |\n| | DE.CM-4: Malicious code is detected."}], "metadata": {"source": "Introduction to Cybersecurity for Commercial Satellite Operations", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Security Analysis of First Responder Mobile and Wearable Devices:\n\n| 6.3 | Structural and environmental incidents......................................................... | 26 |\n|---------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|\n| 7 Threat Analysis ....................................................................................................28 | 7 Threat Analysis ....................................................................................................28 | |\n| 7.1 | Threat Analysis Methodology........................................................................ | 28 |\n| 7.2 | Threats to Public Safety Mobile Devices....................................................... | 31 |\n| 7.3 | Threats to Public Safety Wearable Devices.................................................."}], "metadata": {"source": "Security Analysis of First Responder Mobile and Wearable Devices", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Personal Identity Verification (PIV) of Federal Employees and Contractors support CMMC certification?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\ns to access security-sensitive buildings, information systems, and applications. An accurate determination of an individual's identity supports making sound access control decisions.\nThis document establishes a standard for a Personal Identity Verification (PIV) system that meets the control and security objectives of Homeland Security Presidential Directive-12. It is based on secure and reliable forms of identity credentials issued by the Federal Government to its employees and contractors. These credentials are used by mechanisms that authenticate individuals who require access to federally controlled facilities, information systems, and applications. This Standard addresses requirements for initial identity proofing, infrastructure to support interoperability of identity credentials, and accreditation of organizations and processes issuing PIV credentials. Keywords: authentication, authenticator, biometrics, credential, cryptography, derived PIV credentials, digital identity, Federal Information Processing Standards (FIPS), HSPD-12, federation, identification, identity proofing, integrated circuit card, Personal Identity Verification, PIV, PIV identity account, public key infrastructure, verification\n\n## Federal Information Processing Standards Publication 201-3 January 2022\n\n## Announcing the Standard for\n\n## Personal Identity Verification (PIV) of Federal Employees and Contractors\n\nFederal Information Processing Standards Publications (FIPS PUBS) are issued by the National Institute of Standards and Technology (NIST) after approval by the Secretary of Commerce pursuant to Section 5131 of the Information Technology Management Reform Act of 1996 (Public Law 104-106) and the Computer Security Act of 1987 (Public Law 100-235). 1. Name of Standard."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Science Challenges:\n\n1. Search authority. Legal authority is required to conduct a search and/or seizure of data. 2. Chain of custody. In legal contexts, chronological documentation of access and handling of evidentiary items is required to avoid allegations of evidence tampering or misconduct. 3. Imaging/hashing function. When items containing potential digital evidence are found, each should be carefully duplicated and then hashed to validate the integrity of the copy. 4. Validated tools. When possible, tools used for forensics should be validated to ensure reliability and correctness. 5. Analysis. Forensic analysis is the execution of investigative and analytical techniques to examine, analyze, and interpret the evidentiary artifacts retrieved. - Architecture (e.g., diversity, complexity, provenance, multi-tenancy, data segregation). Architecture challenges in cloud forensics include:\n- o Dealing with variability in cloud architectures between Providers\n- o Tenant data compartmentalization and isolation during resource provisioning\n- o Proliferation of systems, locations, and endpoints that can store data\n- o Accurate and secure provenance for maintaining and preserving chain of custody\n- Data collection (e.g., data integrity, data recovery, data location, imaging). Data collection challenges in cloud forensics include:\n- o Locating forensic artifacts in large, distributed, and dynamic systems\n- o Locating and collecting volatile data\n- o Data collection from virtual machines\n- o Data integrity in a multi-tenant environment where data is shared among multiple computers in multiple locations and accessible by multiple parties\n- o Inability to image all of the forensic artifacts in the cloud\n- o Accessing the data of one tenant without breaching the confidentiality of other tenants\n- o Recovery of deleted data in a shared and distributed virtual environment\n- Analysis (e.g., correlation, reconstruction, time synchronization, logs, metadata, timelines)."}], "metadata": {"source": "NIST Cloud Computing Forensic Science Challenges", "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 Security Assessment?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n| |\n| AM-5: Resources (e.g., hardware, devices, data, time, personnel, and software) are prioritized based on their classification, criticality, and business value. | Determine required resources to support current regulations and standards requirements for the responsible use of PNT systems. Provide adequate staffing with the appropriate training such that PNT support is available in a timely manner (consistent with thresholds defined in the organization's business plan). Formalize PNT roles provide a process for transitioning staff members (with PNT expertise) to be replaced. The remaining staff members are provided with necessary resources and PNT training. Identify and prioritize PNT system components, processors, and functions based on their classification, criticality, and business value. Identify the types of information in the organization's possession, custody, or control for which security safeguards are needed (e.g., sensitive or protected information). Stakeholders are advised to use other functions within the CSF to inform identification procedures. For example, while testing business continuity procedures, use the findings of a lost PNT source to identify which aspects of the mission were impacted and to what degree, and reprioritize accordingly. When identifying resources and prioritizing trade-offs for PNT systems, holistically consider requirements, such as availability, continuity, data integrity, timeliness of anomaly detection, response, and recovery. | 3GPP TS22.071 4 DHS CISA 3 ISO/IEC/IEEE 15939:2017 6.3.2.3 NIST SP 800-37 3 NIST SP 800-53 Rev. 5 AC-20, RA-9 USG FRP Appendix B |"}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does NIST provide for CMMC Level 2?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\n\n\n## NIST Special Publication 800 NIST SP 800-171r3\n\n## Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations\n\nRon Ross Victoria Pillitteri Computer Security Division\n\nInformation Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-171r3\n\nMay 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for Securing Wireless Local Area Networks (WLANs):\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."}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "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 Computer Security Division 2006 Annual Report:\n\nneration of the Voluntary Voting System Guidelines (VVSG), focusing on developing a security architecture that addresses significant threats to voting systems and enhancing voting system auditability.\nNew and updated requirements developed for the next generation of the VVSG cover access control, secure software distribution and installation, setup validation, system event logging, cryptography, voter verified paper records, physical security, and communications. To support the development of the next generation of the VVSG, two workshops on voting system threats were held, and we conducted research to enhance the auditability of voting systems."}], "metadata": {"source": "Computer Security Division 2006 Annual Report", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Security and Privacy Controls in Information Systems and Organizations:\n\nNTROL ASSESSMENTS ..................................................... 30\n3.4 ANALYZE ASSESSMENT REPORT RESULTS .....................................................................................\n32\n3.5 ASSESS SECURITY AND PRIVACY CAPABILITIES .............................................................................. 34\nCHAPTER FOUR SECURITY AND PRIVACY ASSESSMENT PROCEDURES ................................................. 37\n4.1 ACCESS CONTROL............................................................................................................................ 40\n4.2 AWARENESS AND TRAINING ........................................................................................................ 118\n4.3 AUDIT AND ACCOUNTABILITY ...................................................................................................... 128\n4.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 160\n4.5 CONFIGURATION MANAGEMENT ................................................................................................ 177\n4.6 CONTINGENCY PLANNING ............................................................................................................ 215\n4.7 IDENTIFICATION AND AUTHENTICATION .................................................................................... 243\n4.8 INCIDENT RESPONSE ............................................................................................................... 275\n4.9 MAINTENANCE ........................................................................................................................ 298\n4.10 MEDIA PROTECTION .............................................................................................................. 316\n4.11 PHYSICAL AND ENVIRONMENTAL PROTECTION ......................................................................."}], "metadata": {"source": "Assessing Security and Privacy Controls in Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce provide? (Part 5)"}, {"role": "assistant", "content": "urity (NICE Framework) , NIST Special Publication 800-181, Revision 1, and is expected to be read in that context. This document was released in draft form for comment twice prior to this publication.\nThe first draft was released in March 2021, along with an initial list of proposed Competency Areas. A second draft was released in December 2021. Feedback received on those drafts, conversations with NICE community members, and insights from workshops that brought together subject matter experts on this topic have matured understanding of NICE Framework Competency Areas. The adjustments to this document are the result. Any subsequent draft(s) may be further adjusted, including the separately provided Competency Areas, their descriptions, and associated Task, Knowledge, and Skill (TKS) statements. ## Patent Disclosure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| | Introduction ......................................................................................................................"}], "metadata": {"source": "NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guide to Attribute Based Access Control (ABAC) Definition and Considerations:\n\n| Executive Summary ................................................................................................................... | Executive Summary ................................................................................................................... | Executive Summary ................................................................................................................... | vii |\n|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------|\n| 1. Introduction ............................................................................................................................ | 1. Introduction ............................................................................................................................ | 1. Introduction ............................................................................................................................ | 1 |\n| 1.1 | Purpose and Scope ....................................................................................................... | Purpose and Scope ....................................................................................................... | 1 |\n| 1.2 | Audience ........................................................................................................................."}], "metadata": {"source": "Guide to Attribute Based Access Control (ABAC) Definition and Considerations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Privacy Protection in the United States_ A 1991 Survey of Laws and Regulations Affecting Privacy in the Public and Private Sector Including a List of :\n\nthe identity and stated purposes of recipients of consumer reports. 15 U.S.C. § 1681, ei seq . Insurance Records Statutes -Require insurers to provide general information about their personal data practices to applicants and policyholders, with further information available upon request. Also require them to notify applicants about the collection and disclosure of personal data, and to specify when information is requested solely for marketing or research purposes. Restrict the use of \"pretext interviews\" (in which the identity or purpose of the interviewer is misrepresented) and require specific consent forms to be used for the collection of information that requires authorization from an individual. Permit individuals who are denied insurance to learn the specific reasons for such denial and to obtain access to the information used in refusing coverage. 19. Federal statutes prohibit the unauthorized use or disclosure of alcoholism and drug abuse treatment records byprivate clinics receiving Federal funds, except in a medical emergency, for research or audits, or under a court order. 21 U.S.C. § 1175; 42 U.S.C. § 290dd-3. 20. Virtually every State has statutes that limit the use and disclosure of medical or mental health records . See . e . q . Cal. Civ. Code § 56; Colo. Rev. Stat. § 18-4-412; Conn. Gen. Stat. § 52-146h; 111. Stat. ch . 91 1/2. § 801: Mass. Gen. Laws ch. Ill, § TOE; N.M. Stat. § 42-1-15. Pa. Stat. tit. 50, § 7111; R.I. Gen. Laws § 5-37.3.3; Tenn. Code § 10-7-504; Tex. Rev. Civ. Stat. art. 4447d; Wis. Stat. § 146.82. 21. The Family Educational Rights and Privacy Act provides that schools receiving public funds are prohibited from using or disclosing a student's records without the consent of the student (or the parent of a minor student) except for certain specified purposes, or pursuant to a court order or lawfully issued subpoena. 20 U.S.C. § 1232g. 22."}], "metadata": {"source": "Privacy Protection in the United States_ A 1991 Survey of Laws and Regulations Affecting Privacy in the Public and Private Sector Including a List of ", "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 Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio 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\nThe primary audience for this publication is both Federal Government and non-Federal Government professionals at all levels who understand ICT risk management (ICTRM) for one or more ICT domains but may be unfamiliar with ERM. The secondary audience includes both Federal and non-Federal Government corporate officers, high-level executives, ERM officers and staff members, and others who understand ERM but may be unfamiliar with the unique characteristics of ICTRM. All readers are expected to gain an improved understanding of how ICTRM and ERM relate to each other, as well as the benefits of integrating their use. ## Document Conventions\n\nFor this document, 'assets' are defined as technologies that may compose an information or communications system. The term 'asset' or 'assets' is used in multiple frameworks and documents. Examples include laptop computers, desktop computers, servers, sensors, data, mobile phones, tablets, routers, and switches. In instances where the authors mean 'assets' as they might be discussed at the enterprise level, the word 'asset' will be preceded by words such as 'enterprise,' to differentiate context. This document uses the phrase 'information and communications technology' for ICT. As of this writing, both this phrase and the same phrase with 'communication' instead of 'communications' are widely used. The phrases essentially mean the same thing. This document references two types of controls, each of which is essential and should not be confused with the other:\n\n- Internal controls are the overarching mechanisms used to achieve and monitor enterprise objectives."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\n3.2.2 public key size\n\n| Purpose | Co irms that the size of the sed on th nf public key for digital signature used to sign e expiration of the PIV card and is in the biometrics is ba accordance with Table 3-3 of SP80078. 3.2.2 Verify asymmetric key pair\n\n| Purpose | Con that exists in the certificate corresponds to firms that the public key the p e card. 3.2.2: Verify signer public key size | The tester shall validate that the public key size is in accordance with Table 3-3 of SP 800-78."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Integrating Forensic Techniques into Incident Response:\n\nLLC), Marc Rogers (Purdue University), and Miles Tracy (U.S. Federal Reserve System), as well as representatives from the Department of State, for their particularly valuable comments and suggestions.\nBecause of the variety of data sources, digital forensic techniques can be used for many purposes, such as investigating crimes and internal policy violations, reconstructing computer security incidents, troubleshooting operational problems, and recovering from accidental system damage. Practically every organization needs to have the capability to perform digital forensics (referred to as forensics throughout the rest of the guide). Without such a capability, an organization will have difficulty determining what events have occurred within its systems and networks, such as exposures of protected, sensitive data. This guide provides detailed information on establishing a forensic capability, including the development of policies and procedures. Its focus is primarily on using forensic techniques to assist with computer security incident response, but much of the material is also applicable to other situations."}], "metadata": {"source": "Guide to Integrating Forensic Techniques into Incident Response", "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 U.S. Department of Justice Simplified Risk Analysis Guidelines:\n\n- a. Accreditation - Accreditation is the official management authorization to operate an AIS or network in a particular security mode with a proscribed set of administrative, environmental, and technical security safeguards in a given operational environment. - b. Automated Information System (AIS) -An AIS is an assembly of computer hardware, software, and/or firmware configured to collect, create, communicate, compute, disseminate, process, store, or control data or information. An AIS will typically consist of ADP system hardware, operating system and application software, associated peripheral devices, and associated data communications equipment. An AIS includes PCs, work stations, and office automation systems. - c. Network -A network comprises communications media and all attached components whose responsibility is the transfer of information among a collection of AISs or work stations. Network components include packet switches, front-end computers, network controllers, and\n4. technical control devices. - d. Sensitive Application Systems -Systems that process sensitive data or require protection due to the risk and magnitude of loss or harm that could result from improper operation or deliberate manipulation of the application. - b. This step also requires an accurate documentation of the security policies, procedures, and countermeasures currently in effect for the AIS. The security measures in place should include administrative procedures, software and hardware security controls, physical security access controls, personnel security controls, and a security awareness program as listed in Table 2 The current security control environment is important due to its impact on the evaluation of the need for additional security measures. - c. The person conducting the risk analysis should also obtain information on the impact of data disclosure, modification, destruction, and disruption of processing on the component's ability to meet mission objectives."}], "metadata": {"source": "U.S. Department of Justice Simplified Risk Analysis Guidelines", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Stateful Hash-Based Signature Schemes:\n\nThe XMSS and XMSS MT parameter sets that are approved for use by this Special Publication are specified in Sections 5.1 through 5.4. The parameters n , w , len , h , and d specified in the tables are defined in Sections 3.1.1, 4.1.1, and 4.2.1 of [1].\n\nThe private n -byte strings in the WOTS + private keys (sk[i] in Section 3.1.3 of [1]) shall be generated using the pseudorandom key generation method specified in Algorithm 10' in Section 7.2.1: sk[ j ] = PRFkeygen( S\\_XMSS , SEED || ADRS ), where PRFkeygen is as defined in Section 5 for the parameter set being used. 6 The private seed, S\\_XMSS , shall be generated using an approved random bit generator [6], where the instantiation of the random bit generator supports at least 8 n bits of security strength. If more than one XMSS key pair is being created within a cryptographic module (including XMSS keys that belong to a single XMSS MT instance), then a separate random S\\_XMSS shall be generated for each XMSS key pair."}], "metadata": {"source": "Recommendation for Stateful Hash-Based Signature Schemes", "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 Representation of PIV Chain-of-Trust for Import and Export:\n\n[FIPS201] describes three use cases for a chain-of-trust: 1) to extend enrollment, 2) to reissue a PIV Card, and 3) to transfer PIV Card enrollment records to another federal issuer or to a service provider. The purpose of this document is to provide the data representation of a chain-of-trust record for the transferal use case. The data representation is based on a common XML (Extensible Markup Language) schema to facilitate interoperable information sharing and data exchange. The sending and receiving federal agencies will be able to exchange the chain-of-trust data according to the specifications provided in this document. Similarly, a service provider will be able to receive chain-of-trust records from different client agencies that are based on a common XML schema specified in this document. This document also provides support for data integrity through digital signatures and for confidentiality through encryption of chain-oftrust data, in transit and at rest.\n\nAll PIV chain-of-trust records are signed using XML Signature. An XML Signature protects the integrity of the data and authenticates the issuer of the chain-of-trust. A valid"}], "metadata": {"source": "Representation of PIV Chain-of-Trust for Import and Export", "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 Maintenance?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\nNISTIR 8228 explores a number of challenges, grouped around conventional risk mitigation areas such as asset management, data protection, incident detection, and vulnerability management. The publication further groups these areas into goals of protecting device security, data security, and/or individual privacy. Challenges can arise that hinder risk mitigations in various areas or could impact some or all of the goals. For example, to mitigate risks related to vulnerability management, software updates may need to be performed. However, not all IoT devices allow for software updates (Challenges 8, 10, and 11). Even mitigations as simple as hiding passwords might not be achievable on IoT devices (Challenge 17). 3. Will the implementation or maturity of device cybersecurity capabilities and/or nontechnical supporting capabilities fail to satisfy key device cybersecurity requirements? Some IoT devices may completely lack key device cybersecurity requirements, potentially making the IoT device unusable by the organization. Other IoT devices may provide device cybersecurity requirements but not in the manner expected by the organization. For example, an IoT device may have a unique device identifier, but it may not be in a format the organization uses with other equipment. The organization will need to plan for how this identifier will be incorporated into its asset management processes. When an IoT device's cybersecurity capabilities lack maturity, the task of securing the device may be much more difficult. For example, an IoT device may encrypt data, but use a deprecated encryption module due to device resource constraints. In this case, the organization may need to apply significant compensating controls. 4. What are the physical, logical access, network, and other requirements of the IoT device and how do they relate to key device cybersecurity requirements?"}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "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 Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\nList of Abbreviations and Acronyms .........................................................51 | Appendix A. List of Abbreviations and Acronyms .........................................................51 | |\n| Appendix B. Glossary........................................................................................................55 | Appendix B. Glossary........................................................................................................55 | |\n| Appendix C. Additional Resources ..................................................................................58 | Appendix C. Additional Resources ..................................................................................58 | |\n| List of Tables | List of Tables | List of Tables |\n| Table 1. Baseline Profile for the Identify Function......................................................................10 | Table 1."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "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 U.S. Department of Energy Risk Assessment Methodology:\n\n|\n| (*) 1. | PHYSICAL PROTECTION OF SPECIAL NUCLEAR MATERIAL AND VITAL EQUIPMENT | PHYSICAL PROTECTION OF SPECIAL NUCLEAR MATERIAL AND VITAL EQUIPMENT | DOE 5632.2A |\n| m.\n| SECURITY SURVEYS, NUCLEAR MATERIALS SURVEYS AND FACILITY APPROVALS | SECURITY SURVEYS, NUCLEAR MATERIALS SURVEYS AND FACILITY APPROVALS | DOE 5634.1 A |\n| n. | CONTROL OF CLASSIFIED DOCUMENTS AND INFORMATION | CONTROL OF CLASSIFIED DOCUMENTS AND INFORMATION | DOE 5635.1 A |\n| 0. | TECHNICAL SURVEILLANCE COUNTERMEASURES PROGRAM | TECHNICAL SURVEILLANCE COUNTERMEASURES PROGRAM | DOE 5636.3A |\n| P- | CLASSIFIED COMPUTER SECURITY PROGRAM | CLASSIFIED COMPUTER SECURITY PROGRAM | DOE 5637.1 |\n| q- | PHYSICAL PROTECTION OF CLASSIFIED MATTER | PHYSICAL PROTECTION OF CLASSIFIED MATTER | DOE 5632.5 |\n| ( *) r. | PHYSICAL PROTECTION OF DOE PROPERTY AND UNCLASSIFIED FACILITIES | PHYSICAL PROTECTION OF DOE PROPERTY AND UNCLASSIFIED FACILITIES | DOE 5632.6 |\n| ( *) s. | PROTECTIVE FORCES | PROTECTIVE FORCES | DOE 5632.7 |\n| (*) t | PROTECTION PROGRAM OPERATIONS: SYSTEM PERFORMANCE TESTS | PROTECTION PROGRAM OPERATIONS: SYSTEM PERFORMANCE TESTS | DOE 5632.8 |\n| ( *) u."}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "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 Risk Assessment?"}, {"role": "assistant", "content": "According to Security Segmentation in a Small Manufacturing Environment:\n\nTo understand and configure the trusted communication between security zones, the communication requirements between assets must be determined based on a deep understanding of the existing traffic flows between all the assets in the plant or using a network monitoring tool. The traffic flows identified need to be validated for accuracy to detect any spurious traffic that may exist in the environment. A network monitoring tool typically gives a more accurate picture of the actual communication pattern between the assets that exists in the environment. Additionally, incorporating a network monitoring tool as part of the business and plant operation provides continuous visibility into assets, vulnerabilities in those assets, and network traffic. This helps mitigate the 'Poor Visibility of assets and network traffic' vulnerability that typically exists in the small manufacturing environment. - RA - Remote Access. - AAC- Authentication and Access Control\n- BkUp - Back up\n- FW-Firewall\n- VM- Vulnerability Management\n- BAD-Behavior Anomaly Detection\n- EDR- Endpoint Detection and Response\n\n| CSF subcategory | Security Control Description | Solu- tions | Security Zone | Security Zone | Security Zone | Security Zone | Security Zone |\n|-------------------|-------------------------------------------------------------------------|---------------|---------------------------|---------------------------|----------------------------|--------------------------------|-----------------|\n| | | | Connectivity Services (M) | Business Applications (M) | Administrative Systems (H) | Manufacturing Applications (H) | ICS (ICS) |\n| DE.CM-1 | Monitor the network to detect potential cybersecurity events."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Fiscal Year 2024 Cybersecurity and Privacy Annual Report:\n\n- PRIORITY AREAS -\n- Cryptography 5\n- Education & Workforce 7\n- Emerging Technology 9\n- HumanCentered Cybersecurity 11\n- Identity & Access Management 13\n- Privacy 15\n- Risk Management 17\n- Trusted Networks & Platforms 19\n- National Cybersecurity Center of Excellence (NCCoE) 21\n- Stakeholder Engagement & Events 24\n\n## Identity & Access Management\n\n## IDENTITY & ACCESS MANAGEMENT"}], "metadata": {"source": "Fiscal Year 2024 Cybersecurity and Privacy Annual Report", "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 System and Information Integrity?"}, {"role": "assistant", "content": "According to Stateless Hash-Based Digital Signature Standard:\n\n1. Name of Standard. Stateless Hash-Based Digital Signature Standard (FIPS 205). 2. Category of Standard. Computer Security. Subcategory. Cryptography. 3. Explanation. This standard specifies a stateless hash-based digital signature scheme (SLHDSA) for applications that require a digital signature rather than a written signature. Additional digital signature schemes are specified and approved in other NIST Special Publications and FIPS publications (e.g., FIPS 186-5 [1]). A digital signature is represented in a computer as a string of bits and computed using a set of rules and parameters that allow the identity of the signatory and the integrity of the data to be verified. Digital signatures may be generated on both stored and transmitted data. 7. Applications. A digital signature algorithm allows an entity to authenticate the integrity of signed data and the identity of the signatory. The recipient of a signed message can use a digital signature as evidence in demonstrating to a third party that the signature was, in fact, generated by the claimed signatory. This is known as non-repudiation since the signatory cannot easily repudiate the signature at a later time. A digital signature algorithm is intended for use in electronic mail, electronic funds transfer, electronic data interchange, software distribution, data storage, and other applications that require data integrity assurance and data origin authentication. 8. Implementations. A digital signature algorithm may be implemented in software, firmware, hardware, or any combination thereof. NIST will develop a validation program to test implementations for conformance to the algorithms in this standard. For every computational procedure that is specified in this standard, a conforming implementation may replace the given set of steps with any mathematically equivalent process. In other words, different procedures that produce the correct output for every input are permitted."}], "metadata": {"source": "Stateless Hash-Based Digital Signature Standard", "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 Managing Information Security Risk_ Organization, Mission, and Information System View:\n\nadversaries using cyberspace to their advantage and from our own efforts to employ the global nature of cyberspace to achieve objectives in military, intelligence, and business operations... '\n- ' ...\nFor operational plans development, the combination of threats, vulnerabilities, and impacts must be evaluated in order to identify important trends and decide where effort should be applied to eliminate or reduce threat capabilities; eliminate or reduce vulnerabilities; and assess, coordinate, and deconflict all cyberspace operations... '\n- ' ... Leaders at all levels are accountable for ensuring readiness and security to the same degree as in any other domain... '\n- -- THE NATIONAL STRATEGY FOR CYBERSPACE OPERATIONS OFFICE OF THE CHAIRMAN, JOINT CHIEFS OF STAFF, U.S. DEPARTMENT OF DEFENSE"}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "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 Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products provide?"}, {"role": "assistant", "content": "## Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products\n\nNational Institute of Standards and Technology\n\nFebruary 4, 2022\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.CSWP.02042022-2\n\n\n\n## Abstract\n\nExecutive Order (EO) 14028, 'Improving the Nation's Cybersecurity,' tasks the National Institute of Standards and Technology (NIST), in coordination with the Federal Trade Commission (FTC) and other agencies, to initiate pilot programs for cybersecurity labeling. NIST is, among other actions, directed '… to identify IoT cybersecurity criteria for a consumer labeling program…' This document seeks to fulfill this directive by recommending consumer IoT product label criteria, label design and consumer education considerations, and conformity assessment considerations for use by a scheme owner to inform a consumer Internet of Things (IoT) product labeling program. ## Keywords\n\nConsumer IoT; criteria; cybersecurity; executive order; label. ## Disclaimer\n\nAny mention of commercial products or reference to commercial organizations is for information only; it does not imply recommendation or endorsement by NIST, nor does it imply that the products mentioned are necessarily the best available for the purpose. ## Additional Information\n\nFor additional information on NIST's Cybersecurity programs, projects and publications, visit the Computer Security Resource Center. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is also available. Submit comments on this publication to:\n\nlabeling-eo@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)."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 a Secure Enterprise Network Landscape provide? (Part 2)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2022-11-10\n\n## How to Cite this NIST Technical Series Publication:\n\nChandramouli R (2022) Guide to a Secure Enterprise Network Landscape."}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Service Mesh Proxy Models for Cloud-Native Applications:\n\n........5 | 2. Typical Service Mesh Data Plane Capabilities and Associated Proxy Functions .................................5 |\n| 3.\nProxy Models (Data Plane Architectures) in Service Mesh Implementations ....................................7 | 3. Proxy Models (Data Plane Architectures) in Service Mesh Implementations ....................................7 |\n| 4. Data Plane Architecture Threat Scenarios and Analysis Methodology............................................12 | 4. Data Plane Architecture Threat Scenarios and Analysis Methodology............................................12 |\n| 5. Detailed Threat Analysis for Data Plane Architectures...................................................................14 | 5. Detailed Threat Analysis for Data Plane Architectures...................................................................14 |\n| 5.1.1. | Compromised L4 Proxy (TR-1).................................................................................................14 |\n| 5.1.2. | Compromised Application Container (TR-2)...........................................................................14 |\n| 5.1.3. | Compromise of Business Data (TR-3)......................................................................................15 |\n| 5.1.4. | Compromised L7 Proxy (TR-4).................................................................................................15 |\n| 5.1.5. | Compromise of Shared L7 Proxy (TR-5) ..................................................................................15 |\n| 5.1.6."}], "metadata": {"source": "Service Mesh Proxy Models for Cloud-Native Applications", "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 Security Architecture Design Process for Health Information Exchanges (HIEs):\n\n| 5 |\n| Figure 2. HIE Security Architecture Design Process ......................................................................\n| 7 |\n| Figure 3. Enabling Services........................................................................................................... | 13 |\n| Figure 4. Notional Architecture Development Process................................................................. | 22 |\n| Figure 5. Basic Identity and Access Management Components ................................................... | 24 |\n| Figure 6. Web Services Security Standards................................................................................... | 26 |\n| Figure 7. Illustrative Steps from Notional Architecture to Secure HIE Services.......................... | 27 |\n| Figure 8. Regional HIEs with Standard Enabling Services........................................................... | 28 |\n| Figure 9. Multi-Regional HIE with Federated Enabling Services................................................. | 29 |\n| Figure 10. Nationwide HIE with Federated Data Protection Services .......................................... | 29 |\n| Figure 11. Clinical Assessment Scenario of 2008 ONC Personalized Healthcare Use Case......"}], "metadata": {"source": "Security Architecture Design Process for Health Information Exchanges (HIEs)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-204D\n\n## Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines\n\nRamaswamy Chandramouli Frederick Kautz Santiago Torres-Arias\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-204D\n\n\n\n## NIST Special Publication 800 NIST SP 800-204D\n\n## Strategies for the Integration of Software Supply Chain Security in DevSecOps CI/CD Pipelines\n\nRamaswamy Chandramouli Computer Security Division Information Technology Laboratory\n\nFrederick Kautz TestifySec\n\nSantiago Torres-Arias Electrical and Computer Engineering Department Purdue University\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-204D\n\nFebruary 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain commercial equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 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 additional guidance does Computer Security Division 2009 Annual Report provide? (Part 3)"}, {"role": "assistant", "content": "ISO Standardization of Cryptographic ModuleTesting | 18 18 | Security Content Automation Protocol | 39 | 39 | | | | National Checklist Program | 41 | 41 | | Guidelines and Documents | | Security Content Automation Protocol Validation | 43 | 43 | | | | Program | | | | CryptographicTechnology Group | | Technical Security Metrics | 44 | 44 | | | 21 | | 44 | 44 | | Cryptographic Standards Toolkit | 21 21 | Vulnerability Measurement and Scoring Network Security Analysis Using Attach | | | | Hash Algorithms Security Guidelines of Using Approved Hash Algorithms | 21 | Graphs | 44 | 44 | | Digital Signatures Random Number Generation | 22 22 | Infrastructure Services, Protocols, and Applications Internet Protocol Version 6 and Internet Protocol | 45 45 | Security | | | 22 | Securing the Domain Name System Wireless Security Standards | 46 | 46 | | | | | 47 | 47 | | Key Establishment Using | 22 | | | | | Public Key Cryptography Block Cipher Modes of Operation | | CSD's Part in National and International IT Security | | | | Key"}], "metadata": {"source": "Computer Security Division 2009 Annual Report", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide for Conducting Risk Assessments:\n\n## Guide for Conducting Risk Assessments\n\n| CHAPTER ONE INTRODUCTION ..........................................................................................1 | CHAPTER ONE INTRODUCTION ..........................................................................................1 | CHAPTER ONE INTRODUCTION ..........................................................................................1 | |\n|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|\n| 1.1 | PURPOSE AND APPLICABILITY .................................................................................................. | PURPOSE AND APPLICABILITY .................................................................................................. | 2 |\n| 1.2 | TARGET AUDIENCE.................................................................................................................. | TARGET AUDIENCE.................................................................................................................."}], "metadata": {"source": "Guide for Conducting Risk Assessments", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to Fiscal Year 2021 Cybersecurity and Privacy Annual Report:\n\norganization identity cards. The foundation of any data center or edge computing security strategy should be securing the platform on which data and workloads will be executed and accessed.\nThe physical platform represents the first layer for any layered security approach and provides the initial protections to help ensure that higher-layer security controls can be trusted. In FY 2021, the NCCoE continued to develop and demonstrate approaches based on hardware-enabled security techniques and technologies for safeguarding data and workloads. Hardware-Enabled Security: Container Platform Security Prototype (NISTIR 8320A) was finalized in June 2021, and a second public comment draft of Hardware-Enabled Security: Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases (NISTIR 8320) was released in May 2021. Additional publications in the NISTIR 8320 series are also under development."}], "metadata": {"source": "Fiscal Year 2021 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\nControlled Unclassified Information; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; nonfederal organizations; nonfederal systems; organization-defined parameter; security assessment; security control; security requirement.\n\n- Federal agencies responsible for managing and protecting CUI\n- Nonfederal organizations responsible for protecting CUI\n- Individuals with system development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Individuals with acquisition or procurement responsibilities (e.g., contracting officers)\n- Individuals with system, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Individuals with security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, analysts, independent verifiers and validators)\n\n| Access Control | Maintenance | Security Assessment and Monitoring |\n|-----------------------------------|---------------------|--------------------------------------|\n| Awareness and Training | Media Protection | System and Communications Protection |\n| Audit and Accountability | Personnel Security | System and Information Integrity |\n| Configuration Management | Physical Protection | Planning |\n| Identification and Authentication | Risk Assessment | System and Services Acquisition |\n| Incident Response | | Supply Chain Risk Management |"}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n- GLYPH<c=31,font=/HHCKCL+Webdings> Audiovisual Device Monitoring . A few host-based IDPS products can detect when a host's audiovisual devices, such as microphones, cameras, or IP-based phones are activated or used. This could indicate that the host has been compromised by an attacker. - GLYPH<c=31,font=/HHCKCL+Webdings> Host Hardening . Some host-based IDPSs can automatically harden hosts on an ongoing basis. For example, if an application is reconfigured, causing a particular security function to be disabled, the IDPS could detect this and enable the security function. - GLYPH<c=31,font=/HHCKCL+Webdings> Process Status Monitoring . Some products monitor the status of processes or services running on a host, and if they detect that one has stopped, they restart it automatically. Some products can also monitor the status of security programs such as antivirus software. - GLYPH<c=31,font=/HHCKCL+Webdings> Network Traffic Sanitization . Some agents, particularly those deployed on appliances, can sanitize the network traffic that they monitor. For example, an appliance-based agent could act as a proxy and rebuild each request and response that is directed through it. This can be effective at neutralizing certain unusual activity, particularly in packet headers and application protocol headers. Sanitization performed by an appliance can also reduce the amount of reconnaissance the attackers can perform on the host it is protecting. Examples include hiding the servers' OS fingerprints and application error messages. Some products can also prevent sensitive information such as social security numbers and credit card numbers from being displayed on Web server pages."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to PBX Administrator’s Security Standards:\n\nNIST expresses its appreciation to FDIC for their kind permission to publish this report. We also wish to acknowledge the many security professionals who participated in the development of these standards, and in particular: Mr. Brian Seborg, Task Manager; Mr. Earl Bears, Chief, Voice Network Services Unit; Mr. Garrett Mussmann, Chief, Automation Security Unit; Mr. Gary Sarsfield, Chief, Branch Support Section; and Mr. John Laclede, I-NET Program Manager. | Policy | |\n|-----------------------------------------|----------|\n| Section 1: FDIC Telephone | |\n| FDIC Telephone Usage Policy | 1-1 |\n| PBX Protection Policy | 1-1 |\n| Acquisition Policy | 1-1 |\n| Security Incident Reporting Policy | 1-1 |\n| Typical Telephone System Configurations | 1-2 |\n| Terms Used in GS/SYS85 and G1/SYS75 | 1-3 |\n| Section 2: PBX Fraud | |\n| PBX Fraud History | 2-1 |\n| Illegally Obtaining Authorization Codes | 2-2 |\n| Observation | 2-2 |\n| Social Engineering Schemes | 2-2 |\n| Operator Direct Dial Scheme | 2-2 |\n| Call/Sell Operations | 2-3 |\n| Call Diverter Schemes | 2-3 |\n| Remote Access Fraud | 2-3 |\n| Voice Mail Fraud | ."}], "metadata": {"source": "PBX Administrator’s Security Standards", "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 Attribute Considerations for Access Control Systems:\n\n............................................................................. | Introduction............................................................................................................\n| 1 |\n| | 1.1 Purpose.....................................................................................................................................1 | 1.1 Purpose.....................................................................................................................................1 | |\n| | 1.2 Scope........................................................................................................................................2 | 1.2 Scope........................................................................................................................................2 | |\n| | 1.3 Audience ...................................................................................................................................2 | 1.3 Audience ...................................................................................................................................2 | |\n| | 1.4 Document Structure ..................................................................................................................2 | 1.4 Document Structure ..................................................................................................................2 | |\n| 2 | Consideration Elements........................................................................................ | Consideration Elements........................................................................................ | 4 |\n| 3 | Attribute Considerations....................................................................................... | Attribute Considerations......................................................................................."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Report of the Workshop on Cryptography in Support of Computer Security provide? (Part 3)"}, {"role": "assistant", "content": "working group discussed potential weaknesses of the DES, such as the limitations in key length, the non-random structure of the S-boxes, and possible vulnerabilities to less than exhaustion atacks. 2.\nSome participants felt that the 56-bit key was too short against hightechnology, high cost attack. One assertion was made that the algorithm could be sucessfully attacked for a cost of $20 million. It was pointed out that the first workshop on technology included estimates that the actual cost of building a key-extraction machine would be at least $72 million, the completion date would be 1990, the exhaustion time would be approximately 20 hours, and the probability of success would be low. One participant stated that his personal estimate of the cost (actual cost of production to a manufacturer) to build such a machine would be on the order of $200 million, could not be delivered until at least 1981, would produce 1 key per day, would have a low probability of success and that such a machine would never\n\nbe built. Claims were made that the cost would decrease by an order of magnitude every five years. The general response was that in spite of this the key was satisfactory for all security requirements of economic data (money transfers, proprietary data) and that using the algorithm serially (cascading two chips) satisfied all security requirements for data protected by the proposed DES. 3. There was a concern that S-boxes were non-random and the designer stated this to be true. When reasons for the choice of non-random S-boxes were requested, the designer stated:\n- a. Non-random entries were necessary to provide security. - b. The design criteria, independently derived, coincided with some that were classified and the designers agreed not to make them public. - c. Of the possible good S-boxes, these were chosen to minimize combinatorial logic. - d. The draft DES, published by NBS, was exactly as designed and submitted. 4."}], "metadata": {"source": "Report of the Workshop on Cryptography in Support of Computer Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security Assurance Requirements for Linux Application Container Deployments:\n\nThe containers running in the container stack can either be system containers or application containers. A container that behaves like a full OS and runs programs such as sshd (secure session establishment) and syslogd (logging capability) is called a system container, while one that runs only an application is called an application container [2]. This document focuses on\n\nBuilding a TPM architecture is not the only type of approach for providing trust rooted in hardware for the container stack. Another type of approach that has been proposed is to leverage the trusted execution support of some CPU architectures to protect processes running in a container against attacks from sources inside the same container stack. This includes privileged software in the same stack such as the container runtime and host OS kernel [8]. A mechanism or security solution based on this type of approach is discussed and analyzed in section 3.3.\n\nInstalling a container-specific OS (as opposed to a generic OS distribution), keeping OS versions up-to-date and patched, utilizing logging features that can track anomalous accesses to the OS, and any escalation to perform privileged operations form the crux of Host OS countermeasures in the Container Security Guide . In addition to the above countermeasures, it is also a good OS security practice to disable all unused interfaces (Serial or Proprietary) on the host and minimize the user and administrative accounts and groups. In addition to these, there are Linux-specific patches, such as grsecurity [9] and PaX [10], that are available for Linux distributions. All measures combined should provide the following security assurance for the host OS:"}], "metadata": {"source": "Security Assurance Requirements for Linux Application Container Deployments", "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 AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.1.2. 3.1.2. 3.1.2."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n3.3.2 |\n| PROTECT | Identity Management, Authentication and Access Control (PR. 3.3.2."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guidelines on Firewalls and Firewall Policy:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guidelines on Firewalls and Firewall Policy", "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 Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic provide? (Part 2)"}, {"role": "assistant", "content": "imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the products identified are necessarily the best available for the purpose.\n## Contents\n\n| Company Overview.................................................................................................................2 |\n|--------------------------------------------------------------------------------------------------------------------------------------------|\n| Risk Profile ..........................................................................................................................2 |\n| Highlighted Practices in Cyber Supply Chain Management ..................................................2 |\n| Organizational Approach to Supply Chain Risk and Cybersecurity............................................3 |\n| Supplier Management.............................................................................................................3 |\n| Key Aspects of Managing Supplier Relationships .................................................................3 |\n| Measuring Supplier Risk ......................................................................................................4 |\n| Quality Management and Continuous Improvement...........................................................4 |\n| Incident Response and Recovery .........................................................................................4 |\n| Lessons Learned and Improvement Opportunities ..................................................................5 |\n| References ..............................................................................................................................5 |\n\n\n\n## Company Overview\n\nThe Mayo Clinic is an academic, medical non-profit based in Rochester, Minnesota that serves over 1.2 million patients across Arizona, Florida and Minnesota each year."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Security Assurance Requirements for Linux Application Container Deployments provide? (Part 4)"}, {"role": "assistant", "content": "ines and countermeasures have been proposed by NIST through the Application Container Security Guide (NIST Special Publication 800-190) (referred to in this document as the Container Security Guide ).\nThe Container Security Guide identified security threats to the components of the platform hosting the containers and related artifacts involved in building containers and storing them prior to launch. Taking into consideration the overall security implications for the entire ecosystem involving containers, the document also provided security countermeasures for and through six entities including Hardware, Host Operating System (OS), Container Runtime, Image, Registry and Orchestrator. To carry out these recommendations in the form of countermeasures, one or more security solutions are needed. For these security solutions to effectively meet their security objectives, it is necessary to analyze those security solutions and detail the metrics they must satisfy in the form of security assurance requirements. This is the objective and contribution of this document. Linux and its various distributions form the predominant host OS component of the deployed container platforms. Since they are open-source products, sufficient security related information is available to analyze the security solutions that can be configured using features provided by Linux. Hence the focus of this document is on security assurance requirements for security solutions for application containers hosted on Linux. The target audience includes system security architects and administrators who are responsible for the actual design and deployment of security solutions in enterprise infrastructures hosting containerized hosts. ## Table of Contents\n\n| Executive Summary..................................................................................................... | Executive Summary....................................................................................................."}], "metadata": {"source": "Security Assurance Requirements for Linux Application Container Deployments", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 CMVP Approved Non-Invasive Attack Mitigation Test Metrics_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 5)"}, {"role": "assistant", "content": "quirement; vendor evidence; vendor documentation. ## Audience\n\nThis document is focused toward the vendors, testing labs, and CMVP for the purpose of addressing issues in cryptographic module testing.\n## Table of Contents\n\n| 1 | Scope...................................................................................................................1 |\n|-----|-------------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Normative references.........................................................................................1 |\n| 3 | Terms and definitions ........................................................................................1 |\n| 4 | Symbols and abbreviated terms .......................................................................1 |\n| 5 | Document organization......................................................................................2 |\n| 5.1 | General...........................................................................................................................2 |\n| 5.2 | Modifications...................................................................................................................2 |\n| 6 | CMVP-approved non-invasive attack mitigation test metric requirements...2 |\n| 6.1 | Purpose ..........................................................................................................................2 |\n| 6.2 | Approved non-invasive attack mitigation test metrics.....................................................2 |\n\n## 1 Scope\n\nThis document specifies the Cryptographic Module Validation Program (CMVP) modifications of the methods to be used by a Cryptographic and Security Testing Laboratory (CSTL) to demonstrate conformance."}], "metadata": {"source": "CMVP Approved Non-Invasive Attack Mitigation Test Metrics_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products provide? (Part 2)"}, {"role": "assistant", "content": "ybersecurity 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).\n## Table of Contents\n\n| Introduction ............................................................................................................1 | Introduction ............................................................................................................1 | Introduction ............................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| | 1.1 | Background..................................................................................................... 1 |\n| | 1.2 Scheme and Scheme Owner.......................................................................... | 1 |\n| | 1.3 Document Scope and Goals..........................................................................."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog:\n\n| SU - SOFTWARE | UPDATE.................................................................................. 27 |\n|--------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|\n| (UPD) Update Capabilities ............................................................................27 | |\n| (APP) Update Application Support................................................................28 | |\n| CS - CYBERSECURITY STATE AWARENESS..................................................."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "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 Managing Information Security Risk_ Organization, Mission, and Information System View:\n\nSupplemental Guidance: The evaluation of alternative courses of action can include: (i) the expected effectiveness in achieving desired risk response (and how effectiveness is measured and monitored); and (ii) anticipated feasibility of implementation, including, for example, mission/business impact, political, legal, social, financial, technical, and economic considerations. Economic considerations include costs throughout the expected period of time during which the course of action is followed (e.g., cost of procurement, integration into organizational processes at Tier 1 and/or Tier 2, information systems at Tier 3, training, and maintenance). During the evaluation of alternative courses of action, trade-offs can be made explicit between near-term gains in mission/business effectiveness or efficiency and long-term risk of mission/business harm due to compromise of information or information systems that are providing this nearterm benefit. For example, organizations concerned about the potential for mobile devices (e.g., laptop computers) being compromised while employees are on travel can evaluate several courses of action including: (i) providing users traveling to high-risk areas with clean laptops; (ii) removing hard drives from laptops and operate from CDs or DVDs; or (iii) having laptops go through a detailed assessment before being allowed to connect to organizational networks. The first option is highly effective as returning laptops are never connected to organizational networks. While the second option ensures that hard drives cannot be corrupted, it is not quite as effective in that it is still possible that hardware devices (e.g., motherboards) could have been compromised. The effectiveness of the third option is limited by the ability of organizations to detect potential insertion of malware into the hardware, firmware, or software. As such, it is the least effective of the three options."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to 2020 Cybersecurity and Privacy Annual Report:\n\n- NISTIR 8272, Impact Analysis Tool for Interdependent Cyber Supply Chain Risks , describes a prototype solution for filling the gap between an organization's risk appetite and supply chain risk posture by providing a basic measurement of the potential impact of a cyber supply chain event. This tool does not represent a complete C-SCRM solution but is intended to be integrated into or used in concert with tools such as third-party management, enterprise resource planning, and supply chain management. - The Federal Acquisition Security Council, which was created as a requirement of the U.S. Federal Acquisition Supply Chain Security Act of 2018, helps develop policies and processes for agencies to use when purchasing technology products. It recommends C-SCRM standards, guidelines, and practices that NIST should develop. - The Initial Public Draft of NISTIR 8276, Key Practices in Cyber Supply Chain Risk Management: Observations from Industry , provides a high-level summary of practices deemed by subject matter experts to be foundational to an effective C-SCRM program. It is based on an analysis of interviews with companies over several years (leading to the development of 24 case studies), prior NIST research in C-SCRM, and several standards and industry best practices documents. This work builds on the Roadmap for Improving Critical Infrastructure Cybersecurity, a companion document to the NIST Cybersecurity Framework. The NISTIR is based on an analysis of interviews with companies over several years (leading to the development of 24 case studies), prior NIST research in cyber supply chain risk management, and several standards and industry best practices documents."}], "metadata": {"source": "2020 Cybersecurity and Privacy Annual Report", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms provide?"}, {"role": "assistant", "content": "## NISTIR 8320B\n\n## Hardware-Enabled Security:\n\nPolicy-Based Governance in Trusted Container Platforms\n\nMichael Bartock Murugiah Souppaya Haidong Xia Raghu Yeluri Uttam Shetty Brandon Lum Mariusz Sabath Harmeet Singh Alaa Youssef Gosia Steinder Yu Cao Jayashree Ramanathan\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8320B\n\n\n\n## NISTIR 8320B\n\n## Hardware-Enabled Security:\n\nPolicy-Based Governance in Trusted Container Platforms\n\nMichael Bartock Murugiah Souppaya Computer Security Division Information Technology Laboratory\n\nHaidong Xia Raghu Yeluri Uttam Shetty Intel Corporation Santa Clara, California\n\nBrandon Lum Mariusz Sabath Harmeet Singh Alaa Youssef Gosia Steinder IBM Armonk, New York\n\nYu Cao Jayashree Ramanathan Red Hat Raleigh, North Carolina\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8320B\n\nApril 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8320B 41 pages (April 2022)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8320B\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cryptographic Algorithms and Key Sizes for Personal Identity Verification:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\n. No requirement for vendor all validate that the signature algorithm is based on the expiration TE06.03.15.01: The tester sh date of the PIV card and is in accordance with Table 3-4 of SP80078. | DTR from Section 5 | Test Assertion from Section 9 | DTR Description |\n|----------------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|\n| TE05.03.10.01 | 9.1.2.7 Biometric Type Values 9.2.2.7 Biometric Type Values | eld plates The tester shall verify that the Biometric Type fi contains 0x000008 for fingerprint images or tem and 0x000002 for facial images. |\n| TE05.03.11.01 | ric Data Type 9.1.2.8 Biomet 9.1.2.8 Biometric Data Type | tester shall verify that the Biometric Data Type templates and b001xxxxx for facial image. The value is b100xxxxx for processed fingerprint |\n| TE05.03.12.01 | 9.1.2.9 Biometric D Quality ata | The tester shall verify that the value of Biometric Data Quality is between -2 and 100. |\n| TE05.03.12.02 | 9.2.2.9 Biometric D Quality ata | The tester shall verify that the value of Biometric Data Quality is -2 for a facial image. |\n| TE05.03.13.01 | 9.1.2.10 Creator Fie 9.2.2.10 Creator ld Value Field Value | The tester shall verify the Creator field value."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Measuring the Usability and Security of Permuted Passwords on Mobile Platforms:\n\nIt's important to note that password entropy is only useful in password guessing attacks. Entropy is not an effective metric for determining resistance against keylogging and phishing attacks. Higher entropy passwords may be slightly more secure against shoulder surfing attacks as longer and more complex passwords are often more difficult to capture by the human eye from a distance. However, as technology advances, even these longer passwords may not be secure against automated shoulder surfing tools and new computer vision algorithms [12]."}], "metadata": {"source": "Measuring the Usability and Security of Permuted Passwords on Mobile Platforms", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce:\n\n1 The NICE Framework building block statements, Work Roles, and Competency Areas are made available online as part of the NICE Framework Resource Center in order to allow for regular review and updates [2].\n\n5 The creation and maintenance of NICE Framework Competency Areas follows NIST practices of engaging with stakeholders in an open, transparent, and collaborative process that includes workshops and other opportunities to provide input. Information on how to engage with the NICE Framework, the revision process, and the current List of Competency Areas can be found in the NICE Framework Resource Center: https://www.nist.gov/nice/framework.\n\nNICE Framework resources, including the latest list of Competency Areas, are available in the NICE Framework Resource Center. NIST is maintaining the Competency Areas list separate from this document and from the NICE Framework publication to allow for regular review and updates. The NICE Framework Resource Center also includes information on how to engage in and keep informed on updates and development of the NICE Framework and supporting resources."}], "metadata": {"source": "NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce", "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 Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services provide? (Part 5)"}, {"role": "assistant", "content": "However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication.\nAs of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| | Introduction ......................................................................................................................"}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 De-Identifying Government Datasets_ Techniques and Governance:\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 800series 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 . . . . . . . . . . | . . . . . . . . . . . | 1 |\n|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1. Introduction . . . . . . . . . | 1. Introduction . . . . . . . . . | . . . . . . . . . . . . . . | 3 |\n| 1.1. Document Purpose and Scope | 1.1. Document Purpose and Scope | . . . . . . . . . | 7 |\n| 1.2. Intended Audience . . | 1.2. Intended Audience . . | . . . . . . . . . . . . . . | 7 |\n| 1.3. Organization . . . . | 1.3. Organization . . . . | . . . . . . . . . . . . . . ."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nfunction of the adverse impacts that arise if the circumstance or event occurs, and the likelihood of occurrence. Types security and privacy risk (including supply chain risk); project risk; reputational risk; safety risk; strategic planning risk. 6 [OMB A-130] defines PII as 'information that can be used to distinguish or trace an individual's identity, either alone\n\nThe authorization boundary defines the system 36 for RMF execution to facilitate risk management and accountability. The system may be supported by one or more enabling systems that provide support during the system life cycle. Enabling systems are not contained within the authorization boundary of the system and do not necessarily exist in the system's environment of operation. An enabling system may provide common (i.e., inherited) controls for the system or may include any type of service or functionality used by the system such as identification and authentication services, network services, or monitoring functionality. Finally, there are other systems the system interacts with in the operational environment. The other systems are also outside of the authorization boundary and may be the beneficiaries of services provided by the system or may simply have some general interaction. 37\n\nDiscussion: Common controls are controls that can be inherited by one or more information systems. 60 Common controls can include controls from any [SP 800-53] control family, for example, physical and environmental protection controls, system boundary and monitoring controls, personnel security controls, policies and procedures, acquisition controls, account and identity management controls, audit log and accountability controls, or complaint management controls for receiving privacy inquiries from the public. Organizations identify and select the set of common controls and allocate those controls to the organizational entities designated as common control providers."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to Hardware Security Failure Scenarios_ Potential Hardware Weaknesses:\n\ngions and perform both read and write by using memory alias addresses (i.e., redundant addresses that point to the same memory region) or mirrored memory regions that do not have the same protections.\nAn attacker could possibly create memory address aliases to perform such an attack [CWE-1257]. 9. Lower privilege software can write to memory regions for higher privileged software due to overlapping memory regions, thus enabling malicious software to perform privilege escalation or a DoS attack [CWE-1260]."}], "metadata": {"source": "Hardware Security Failure Scenarios_ Potential Hardware Weaknesses", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n'We depend on pulling in other resources to help with [the security awareness program], and that, again, goes back to being tied to the threat team and to the policy team.' (D03)"}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.7 (NIST 3.1.7)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.1.7. 3.1.7): Proof of possession\n\nand control via an authentication protocol of a cryptographic key held by the\nsubscriber that requires activation by a second authentication factor\n\n2. 3.1.7)\n\nWhen a combination of two single-factor authenticators is used, the combination SHALL\ninclude one physical authenticator (i."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.1.7", "cmmc_practice_id": "AC.L2-3.1.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 Access Control?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\nAn information system 'is a set of interacting elements that are organized to achieve one or more stated purposes.' [ISO15288] Information systems are defined by the authorization boundary 8 , which for systems will encapsulate elements owned and operated by organizations. The information system can also be supported by other enabling systems, which will fall outside the authorization boundary. Information systems can also interact with other systems, which might be beneficiaries of capabilities offered by the information system. The system, as defined by the authorization boundary-as well as some enabling systems and other systems -will fall within the environment of operation, which is the physical environment in which these systems reside and operate. As explained in SP 800-37 Rev. 2, organizations define and determine the parts of the environment of operation that are within the authorization boundary of each federal system. Figure 1 shows how the environment of operation can contain multiple authorization boundaries, including other systems and enabling systems. Elements, including IoT devices, may interact and communicate across multiple systems/authorization boundaries. However, for accountability and risk management purposes, each IoT device is only included within one authorization boundary. 9 Additional enabling systems will fall outside of the environment of operation (e.g., a system hosted by another organization or service provider). This concept of systems and elements can help clarify the ways IoT devices might be used by organizations and the subsequent identification of device cybersecurity requirements. Some IoT devices should be characterized as an enabling or other system if the device is managed in a different authorization boundary than the organization's system. 10 An example of this type of other system might be a building or campus monitoring system that is primarily autonomous."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.12 (NIST 3.6.12)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\n3.6.12. 3.6.12. 3.6.12."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "cmmc_level": "all", "nist_control": "3.6.12", "cmmc_practice_id": "IR.L2-3.6.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 additional guidance does A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N provide? (Part 4)"}, {"role": "assistant", "content": "tandards with similar goals and objectives. An objective of both is to provide a standardized way for expressing and enforcing vastly diverse access control policies on various types of data services.\nHowever, the two standards differ with respect to the manner in which access control policies are specified and implemented. This document describes XACML and NGAC, and then compares them with respect to five criteria. The goal of this publication is to help ABAC users and vendors make informed decisions when addressing future data service policy enforcement requirements. ## Keywords\n\naccess control; access control mechanism; access control model; access control policy; attribute based access control (ABAC); authorization; Extensible Access Control Markup Language (XACML); Next Generation Access Control (NGAC); privilege\n\n## Acknowledgements\n\nThe authors, David Ferraiolo, Ramaswamy Chandramouli, Vincent C. Hu, and Rick Kuhn of the National Institute of Standards and Technology (NIST), wish to thank their colleagues who reviewed drafts of this document, including the following: Karen Scarfone (Scarfone Cybersecurity), Wayne Jansen (Bayview Behavioral Consulting), Serban Gavrila (NIST), Indrakshi Ray (Colorado State University), Duminda Wijesekera (George Mason University), and Ram Krishnan (University of Texas at San Antonio). The authors also gratefully acknowledge and appreciate the comments and contributions made by government agencies, private organizations, and individuals in providing direction and assistance in the development of this document. ## Note to Readers\n\nFor purposes of transparency, one of the authors of this document, David Ferraiolo, is a member of the American National Standards Institute/International Committee for Information Technology (ANSI/INCITS) Next Generation Access Control (NGAC) working group."}], "metadata": {"source": "A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\nthat blend station, electricity, and vehicle charging sales together. Third parties are individuals or entities that facilitate transactions but are not one of the primary parties within the exchange.\nThe EV/XFC ecosystem typically uses cloud service providers for these transactions because they are suitable for sensitive data exchanges that involve financial information, personally identifiable information (PII), and other potentially sensitive data. - Utilities/Building Systems . Utilities provide the power necessary to fuel the EV/XFC ecosystem. Building and facility management systems may be present in installations where energy management is required, such as EVSE installed at shopping centers, as well as where distributed energy resources (DER) may be present or where physical security control is required. Both utilities and building/facility management systems include equipment to monitor power utilization, communicate with networked devices and supervisory systems, and help control on-site energy demands."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs:\n\nmany other rules like the one above in the knowledge base. All the rules form a Datalog program, and a Prolog system can efficiently evaluate such a program against thousands of input tuples.\nThe evaluation process will find out all consequences arising from these rules. Complex multistep, multi-host attack paths are naturally captured in this logical reasoning process, even though each rule itself only describes a specific type of attack."}], "metadata": {"source": "Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs", "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 Program Review for Information Security Management Assistance (PRISMA) provide? (Part 3)"}, {"role": "assistant", "content": "thank the many people who assisted with the development of this handbook. NIST management officials who supported this effort include: Joan Hash, William C. Barker, Elizabeth Chew, and Matthew Scholl.\nThe authors would like to thank Matthew Scholl, and Craig Russell who assisted with reviewing this document and provided comments and suggestions for improvement. In addition, special thanks are due those contractors who helped craft the PRISMA NISTIR, prepare drafts, and review materials:\n\nJessica Gulick of Science Applications International Corporation, (SAIC) served as Project Manager for SAIC on this project. In addition, many SAIC and System 1, Inc. employees contributed to the PRISMA NISTIR, including: Jim Fahlsing, SAIC, Steve Batdorff, System 1, Inc.,Charles M. Cramer, Jr., SAIC, John Abeles, System 1, Inc.,Steve Senz, System 1, Inc.,Michael Pheil, SAIC, Anjali Mulchandani, SAIC, and Rich Sella, SAIC. Special thanks to SAIC's Jessica Gulick, Amy Palmer, and Michael Pheil for their diligent review and editorial support of this document. For all the hard work on the PRISMA database, the authors would like to thank Charles M. Cramer, Jr, Steve Batdorff, and Michael Pheil. In memory of Charles M. Cramer, Jr. Semper Fi\n\nThe authors also gratefully acknowledge and appreciate the many contributions from individuals in the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication. 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 NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## This page is intentionally blank\n\n## T A B L E O F C O N T E N T S\n\n| 1."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n3.2.1. 3.2.1. 3.2.1."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines for the Secure Deployment of IPv6:\n\n..................................................................... | Introduction ...................................................................................................................\n| 1-1 |\n| 1.2 | Authority.................................................................................................................1-1 Scope................................................................................................1-1 | Authority.................................................................................................................1-1 Scope................................................................................................1-1 | |\n| 1.3 | Purpose and Audience ................................................................................................................1-1 | Purpose and Audience ................................................................................................................1-1 | |\n| 1.4 | | | |\n| 2."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\nion understands its dependencies and partners and receives information from these partners that enables collaboration and risk-based management decisions within the organization in response to events.\n| Function | Category | Subcategory | Informative References |\n|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| IDENTIFY (ID) | Asset Management (ID.AM): The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to business objectives and the organization's risk strategy."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "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 Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\ning, implementing, maintaining, and improving information security management of the organization. It is a documented set of the organization's security policies, procedures, guidelines and standards.\nThe program is intended to protect the confidentiality, integrity and availability of information resources."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "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 FIPS 140-3 Derived Test Requirements (DTR)_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 3)"}, {"role": "assistant", "content": "raft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity 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 Email: sp800-140-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\nNIST Special Publication (SP) 800-140 specifies the modifications of the Derived Test Requirements (DTR) for Federal Information Processing Standard (FIPS) 140-3. SP 800-140 modifies the test (TE) and vendor (VE) evidence requirements of International Organization for Standardization/International Electrotechnical Commission (ISO/IEC) 24759."}], "metadata": {"source": "FIPS 140-3 Derived Test Requirements (DTR)_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Representation of PIV Chain-of-Trust for Import and Export provide? (Part 3)"}, {"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 http://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Email: piv\\_comments@nist.gov\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis document provides a common XML-based data representation of a chain-of-trust record to facilitate the exchange of Personal Identity Verification (PIV) Card enrollment data."}], "metadata": {"source": "Representation of PIV Chain-of-Trust for Import and Export", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to 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 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Block Cipher Modes of Operation_ Methods for Format-Preserving Encryption:\n\nMethods for Format -Preserving Encryption\n\nMethods for Format-Preserving Encryption\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: encryptionmodes@nist.gov"}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Methods for Format-Preserving Encryption", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Trustworthy Email:\n\n3.1.2 | Unauthorized Email Receiver within an Organization's IP Address Block... 3.1.2 Unauthorized Email Receiver within an Organization's IP Address Block\n\nUnauthorized mail receivers are a risk to the enterprise IT security posture because they may be an entry point for malicious email. 3.1.2."}], "metadata": {"source": "Trustworthy Email", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n## Guidelines for Media Sanitization\n\n## Guidelines for Media Sanitization\n\nChandramouli R, Hibbard EA (2025) Guidelines for Media Sanitization. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-88r2. https://doi.org/10.6028/NIST.SP.800-88r2"}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\n3.5.1. 3.5.1. 3.5.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Guidelines for Securing Radio Frequency Identification (RFID) Systems:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guidelines for Securing Radio Frequency Identification (RFID) Systems", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions provide? (Part 2)"}, {"role": "assistant", "content": "HA-3 family consists of four cryptographic hash functions, called SHA3-224, SHA3-256, SHA3-384, and SHA3-512, and two extendable-output functions (XOFs), called SHAKE128 and SHAKE256.\nHash functions are components for many important information security applications, including 1) the generation and verification of digital signatures, 2) key derivation, and 3) pseudorandom bit generation. The hash functions specified in this Standard supplement the SHA-1 hash function and the SHA-2 family of hash functions that are specified in FIPS 180-4, the Secure Hash Standard. Extendable-output functions are different from hash functions, but it is possible to use them in similar ways, with the flexibility to be adapted directly to the requirements of individual applications, subject to additional security considerations. Key words : computer security, cryptography, extendable-output function, Federal Information Processing Standard, hash algorithm, hash function, information security, KECCAK, message digest, permutation, SHA-3, sponge construction, sponge function, XOF. ## Federal Information Processing Standards Publication 202\n\n## August 2015\n\n## Announcing the\n\n## SHA-3 STANDARD: PERMUTATION-BASED HASH AND EXTENDABLE OUTPUT FUNCTIONS\n\nFederal Information Processing Standards Publications (FIPS PUBS) are issued by the National Institute of Standards and Technology (NIST) after approval by the Secretary of Commerce pursuant to Section 5131 of the Information Technology Management Reform Act of 1996 (Public Law 104-106), and the Computer Security Act of 1987 (Public Law 100-235). 1. Name of Standard : SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions (FIPS PUB 202). 2. Category of Standard : Computer Security Standard, Cryptography. 3. Explanation : This Standard (FIPS 202) specifies the Secure Hash Algorithm-3 (SHA-3) family of functions on binary data."}], "metadata": {"source": "SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cybersecurity Framework Profile for Liquefied Natural Gas:\n\n| Table 17. Summary Table of Mission Objectives with Protect Function Category Priorities...... | 22 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 18. Summary Table of Mission Objectives with Detect Function Category Priorities....... | 23 |\n| Table 19. Summary Table of Mission Objectives with Respond Function Category Priorities... | 23 |\n| Table 20. Summary Table of Mission Objectives with Recover Function Category Priorities.... | 23 |\n| Table 21. CSF Subcategory Priorities for the Identify Function's Asset Management (ID.AM) | Category........................................................................................................................................23 |\n| Table 22."}], "metadata": {"source": "Cybersecurity Framework Profile for Liquefied Natural Gas", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to U.S. Department of Energy Risk Assessment Methodology:\n\n- Sensitive information disclosed when computer operator forgets to lock the computer facility at end of the day.\n- Computer supplies destroyed when employee stores them in a damp area.\n- Computer facility damaged when maintenance personnel accidentally set off Halon fire suppression system.\n- Building becomes inaccessible when a toxic gas is released.\n\n- Peripheral equipment damaged by disk head crash\n- Storage media destroyed by accidentally spilling coffee on the media\n- Classified information disclosed through release of malfunctioning storage media to maintenance personnel prior to degaussing\n- Use of hardware denied because operator failed to follow proper start-up procedures.\n\n- Documentation is damaged because of extreme humidity.\n- Routine maintenance checks of sprinkler system are neglected after staff reductions occur, leading to a costly repair."}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2005 Annual Report:\n\n| Welcome Letter | 1 |\n|-----------------------------------------------------|-----|\n| Division Organization | 2 |\n| The Computer Security Division Responds to the | |\n| Federal Information Security Management Act of 2002 | 3 |\n| Outreach, Awareness, and Education | 4 |\n| Security Management and Guidance | 9 |\n| Security Testing and Metrics | 16 |\n| Security Research and Emerging Technologies | 21 |\n| Cryptographic Standards and Applications | 36 |\n| Honors and Awards | 44 |\n| Computer Security Division Publications - 2004 | 46 |\n| Ways to Engage Our Division and NIST | 48 |\n\nSecurity Testing & Metrics Group\n\n- Methods for assessing effectiveness of security requirements - SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems (first public draft issued July 2005). - Procedures for capturing results of security requirement assessments and results of security program assessments - SP 800-26 Revision 1, Guide for Information Security Program Assessments and System Reporting Form (first public draft issued August 2005). - Bring the security planning process up to date with key standards and guidelines developed by NIST - SP 800-18 Revision 1, Guide for Developing Security Plans for Federal Information Systems (first public draft issued August 2005)."}], "metadata": {"source": "Computer Security Division 2005 Annual Report", "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 Automation Support for Security Control Assessments_ Volume 1_ Overview:\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 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 systems. The authors, Kelley Dempsey of the National Institute of Standards and Technology (NIST), Dr. George Moore of the Applied Physics Laboratory at Johns Hopkins University, and Paul Eavy of the Department of Homeland Security, wish to thank their colleagues who reviewed drafts of this document, including Nadya Bartol, Craig Chase, Ann Dixon, Terry Fletcher, Jim Foti, Susan Hansche, Amy Heydman, Alicia Jones, Betsy Kulick, Elizabeth Lennon, Susan Pagan, Daniel Portwood, Ron Ross, Martin Stanley, Kevin Stine, Robin Walker, David Waltermire, Kimberly Watson, and Jim Wiggins."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171 provide? (Part 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms:\n\ny infrastructure (PKI) that is responsible for issuing certificates to certificate subjects and exacting compliance to a PKI policy. |\n| Ciphertext | Data in its encrypted form.\n|\n| Compromise | The unauthorized disclosure, modification, substitution, or use of sensitive data (e.g., a secret key, private key, or secret metadata). |\n| Confidentiality | The property that sensitive information is not disclosed to unauthorized entities (i.e., the secrecy of key information is maintained). |\n| Cross-certify | The establishment of a trust relationship between two Certification Authorities (CAs) through the signing of each other's public key in certificates; referred to as a 'cross- certificate.' |\n| Cryptographic algorithm | A well-defined computational procedure that takes variable inputs, including a cryptographic key (if applicable), and produces an output. |\n| Cryptographic boundary | An explicitly defined continuous perimeter that establishes the physical bounds of a cryptographic module and contains all the hardware, software, and/or firmware components of a cryptographic module. |\n| Cryptographic checksum | A mathematical value created using a cryptographic algorithm that is assigned to data and later used to test the data to verify that the data has not changed. |\n| Cryptographic hash function | A function that maps a bit string of arbitrary length to a fixed- length bit string. Approved hash functions satisfy the following properties: |"}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms", "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 A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS) provide? (Part 5)"}, {"role": "assistant", "content": "umed by one or more authorized individuals when managing and using cryptographic key management services are collectively called a Cryptographic Key Management System (CKMS). This Profile for U. S.\nFederal Cryptographic Key Management Systems (FCKMSs) has been prepared to assist CKMS designers and implementers in selecting the features to be provided in their 'products,' and to assist federal organizations and their contractors when procuring, installing, configuring, operating, and using FCKMSs. Other organizations may use this Profile as desired. An FCKMS can be owned and operated by a federal organization or by a private contractor that provides key management services for federal organizations or other contractors performing federal information-processing services. This Profile can also be used by agencies and organizations to understand their FCKMSs, and to adopt, adapt and migrate their FCKMSs to comply with the Profile requirements over time. NIST does not expect that these requirements would be implemented immediately, but that agencies would use these requirements when creating or procuring FCKMSs or FCKMS services for their Enterprise Architectures. This Profile is based on NIST Special Publication 800-130, A Framework for Designing Cryptographic Key Management Systems . The Framework specifies topics that should be considered by a CKMS designer when selecting the capabilities that a CKMS will have and the cryptographic key management services it will support. This Profile replicates all of the Framework requirements that must be satisfied in a CKMS and its design documentation, and includes additional information about installing, configuring, operating and maintaining an FCKMS."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Standard Security Label for GOSIP_ an Invitational Workshop:\n\nSeveral researchers, including Page, Heaney, Adkins, and Dolsen of Planning Research Corporation^ and Abrams, LaPadula, Eggers and Olsen of MITRE^ , have been exploring Rule-Based access control policies. The Rule-Based concept permits security policies to be implemented as sets of rules, and modified as needed without modifying the architecture of the secure system. This promising approach"}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Computer Security Division 2005 Annual Report provide?"}, {"role": "assistant", "content": "\n\n## TABLE OF CONTENTS\n\n| Welcome Letter | 1 |\n|-----------------------------------------------------|-----|\n| Division Organization | 2 |\n| The Computer Security Division Responds to the | |\n| Federal Information Security Management Act of 2002 | 3 |\n| Outreach, Awareness, and Education | 4 |\n| Security Management and Guidance | 9 |\n| Security Testing and Metrics | 16 |\n| Security Research and Emerging Technologies | 21 |\n| Cryptographic Standards and Applications | 36 |\n| Honors and Awards | 44 |\n| Computer Security Division Publications - 2004 | 46 |\n| Ways to Engage Our Division and NIST | 48 |\n\n\n\nT his year the Computer Security Division (CSD) continued its efforts to improve information system security. This effort was accomplished through raising awareness of information technology risks, vulnerabilities, and protection requirements-particularly for new and emerging technologies. We continued to research, study, advise Agencies of IT vulnerabilities, and devise techniques for the cost-effective security and privacy of sensitive Federal systems. We continued to develop standards, metrics, tests, and validation programs to promote, measure, and validate security in systems and services. We also developed guidance to increase secure IT planning, implementation, management, and operation. This effort was conducted to assist our everexpanding customer base that now includes federal, state, and local governments, the healthcare community, colleges and universities, small businesses, the private sector, and the international community."}], "metadata": {"source": "Computer Security Division 2005 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What 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": "How does Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop support CMMC certification?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop:\n\nes 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. ## 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 Email: 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\nThis report summarizes the feedback received on the work of the NIST Cybersecurity for IoT program on device cybersecurity at a virtual workshop in July 2020."}], "metadata": {"source": "Workshop Summary Report for “Building the Federal Profile For IoT Device Cybersecurity” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to An Industrial Control System Cybersecurity Performance Testbed:\n\n3.5.2 | 3. 3.5.2 Ixia Traffic Generator\n\nThe Ixia M2 can be leveraged for executing denial of service (DoS) and replay attacks on the simulated networks."}], "metadata": {"source": "An Industrial Control System Cybersecurity Performance Testbed", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers:\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\nWhen planning security, it is essential to first define the threats that must be mitigated. Organizations that use checklists should conduct risk assessments to identify the specific threats against their systems and determine the effectiveness of existing security controls in counteracting the threats; they then should perform risk mitigation to decide what additional measures (if any) should be implemented, as discussed in NIST SP 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach [6]. Performing risk assessments and mitigation helps organizations better understand their needs and decide whether or not they need to modify or enhance selected checklists."}], "metadata": {"source": "National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers", "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.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Guidelines for Securing Radio Frequency Identification (RFID) Systems:\n\n3.3.4 provides more information on tamper protection. 3.3.4. 3.3.4 Tamper Resistance\n\nControl: Certain RFID tags have tamper resistant or tamper-evident features that help prevent an adversary from altering the tags or removing them from the objects to which they are attached."}], "metadata": {"source": "Guidelines for Securing Radio Frequency Identification (RFID) Systems", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.10 (NIST 3.3.10)?"}, {"role": "assistant", "content": "According to Guide to Operational Technology (OT) Security:\n\n3.3.10. 3.3.10. 3.3.10."}], "metadata": {"source": "Guide to Operational Technology (OT) Security", "cmmc_level": "all", "nist_control": "3.3.10", "cmmc_practice_id": "AU.L2-3.3.10", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Fiscal Year 2021 Cybersecurity and Privacy Annual Report:\n\nA series of 'case studies' was created to enable a small business to educate its employees about common cybersecurity risks. Each case study is limited to a single printable page and is designed to provide sufficient information to allow a discussion of the topic's relevance to the organization. The topics include phishing, social engineering, keystroke logging, encryption, and data breaches.\n\nWith the publication of the third set of conformance criteria for Federation and Assertions (SP 800-63C), following on the release of conformance criteria for volumes SP 800-63A and SP 800-63B in June 2020, the full set of conformance criteria for all volumes of SP 800-63-3 has been completed. The conformance criteria present all normative requirements and controls for the SP 800-63A, B, and C and provide supplemental guidance, control objectives, and recommended test and conformance assessment methods for all of the normative requirements and controls at the designated assurance levels. The conformance criteria are used by federal agencies, independent assessment and certification bodies, auditors, and implementers so that all of the normative requirements and controls for SP 800-63-3 are understood for proper implementation, conformance assessment, and audit.\n\nThe Privacy-Enhancing Cryptography project promotes the use of cryptographic protocols that enable parties to interact meaningfully without revealing private information to one another or to third parties. Toward this end, NIST has been engaged with various stakeholders, researchers, and developers. In FY 2021, motivated by the need to conduct automated exposure notification related to the current pandemic, NIST developed a privacy-protecting method to measure levels of interaction within a population. NIST also launched a quarterly series of talks on topics related to privacy and public auditability."}], "metadata": {"source": "Fiscal Year 2021 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n- A method to identify opportunities for improving the current cybersecurity posture of the manufacturing system\n- An evaluation of their ability to operate the control environment at their acceptable risk level\n- A standardized approach to preparing the cybersecurity plan for ongoing assurance of the manufacturing system's security\n\n| Function | Category | Subcategory | Manufacturing Profile Guidance | Reference |\n|------------|----------------------|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|\n| IDENTIFY | Supply Chain (ID.SC) | ID.SC-3 | Low Impact Implement contractual cybersecurity requirements for suppliers and third-party partners requiring access to sensitive information or providing information technology, operational technology, services, technology-based input products, or non-technology-based input products supporting the manufacturing system. Cyber supply chain risk assessment results should be used in the development of cybersecurity requirements."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security_ Selected Articles:\n\nBy grandfathering, you use a schedule that insures that you won't lose important data, even if you are hit by a virus. First, make a baseline backup so every file on the LAN is backed up. It is the basis you'll use if you must restore the entire system. Second, make daily backups, which you keep until the end of the week. At week's end, you do the weekly back up, which you keep for a month. Return the daily tapes to use for next week's backups.\n\nNow, each month, do a monthly backup, which you keep for a year. Thus, you have four dailies. On Friday, you keep a weekly. At the end of the month, you have four weeklies. At the end of the year, you have 12 monthlies. And you always have the baseline backup. Only back up files that change (incremental backup). Then when you need to restore an entire drive, you start with the baseline and then update with the most recent incremental backup. If you find a virus in your backup, you can move to an earlier backup (that's why you grandfather) and the worst you'll have to do is reenter a month's worth of data."}], "metadata": {"source": "Computer Security_ Selected Articles", "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 Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4):\n\n| Index | Event | Ref |\n|---------|----------------------------------------------------------------|------------|\n| SERI | An improperly protected TPDU received shall be discarded. | 6.0 |\n| SER2 | A TPDU with an invalid key identifier shall be discarded. | 6.2.3 |\n| SER3 | A TPDU with an invalid ICV shall be discarded. | 6.3. 1.3 |\n| SER4 | A TPDU with an invalid direction indicator shall be discarded. | 6.3.2.3 |\n| SER5 | A TPDU with an improper label shall be discarded. | 6.5.3 |\n| SER6 | A TPDU with an improper pad shall be discarded. | 6.2.3 |\n| SER7 | A TPDU with a duplicate sequence number shall be discarded. | 6.3.3. 1.2 |\n| SERB | A TPDU with an invalid peer address shall be discarded. | 6.4 |\n\n| Index | Event | Ref | Action | Action |\n|---------|---------------------------------------------------------------------------------------------------------------------------------------|-----------|------------------------------|-----------|\n| | | | Allowed | Supported |\n| SER9 | An invalid final sequence number detected for an encapsulated DR, DC, or ER TPDU. | 6.3.3.2.3 | Local Matter; Audit Advised. | |\n| SERIO | An invalid destination address, inconsistent with that negotiated for the associated key identifier, appears on an encapsulated TPDU. | None | Open | |"}], "metadata": {"source": "Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759 provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Security Functions_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guidelines on Security and Privacy in Public Cloud Computing:\n\nning and enable better automation of security management activities like configuration control, vulnerability testing, security audits, and security patching of platform components.\nInformation assurance and security response activities also profit from a uniform, homogeneous cloud infrastructure, as do system management activities, such as fault management, load balancing, and system maintenance. Similarly, infrastructure homogeneity benefits management controls employed to protect privacy. On the other hand, homogeneity means that a single flaw will be manifested throughout the cloud, potentially impacting all tenants and services. Many cloud computing environments meet standards for operational compliance and certification in areas such as healthcare (e.g., Health Insurance Portability and Accountability Act (HIPAA)), finance (e.g., Payment Card Industry Data Security Standard (PCI DSS)), security (e.g., ISO 27001, Information Security Management Systems - Requirements), and audit (e.g., Standards for Attestation Engagements (SSAE) No. 16), and may attain formal certification or attestation from an independent third party, to impart a level of assurance with regard to some recognized and generally accepted criteria. -  Resource Availability. The scalability of cloud computing facilities allows for greater availability. Redundancy and disaster recovery capabilities are built into cloud computing environments and on-demand resource capacity can be used for better resilience when faced with increased service demands or distributed denial of service attacks, and for quicker recovery from serious incidents. When an incident occurs, an opportunity also exists to contain attacks and capture event information more readily, with greater detail and less impact on production."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Security Property Verification by Transition Model:\n\n(2016) NPTEL National Program on Technology Enhanced learning . Available at https://www.youtube.com/watch?v=\\_2E5Q3CZ7g4&t=56s [YC2] CTL (2016) National Program on Technology Enhanced learning .\nAvailable at https://www.youtube.com/watch?v=Blh060Hgbm8 [ZL] Potter B, Sinclair J, Till D (1996) An Introduction to Formal Specification and Z (Prentice Hall PTR, Upper Saddle River, NJ), 2nd Ed. Available at https://dl.acm.org/doi/10.5555/547639"}], "metadata": {"source": "Security Property Verification by Transition Model", "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 An Industrial Control System Cybersecurity Performance Testbed provide? (Part 5)"}, {"role": "assistant", "content": "| Traffic Manipulation Tools for Linux ............................................................................................18 |\n|------------|---------------------------------------------------------------------------------------------------------------------------------------------------|\n| Table 2. | Categories of Industrial Processes ...............................................................................................19 |\n| Table 3. | List of Terms .................................................................................................................................23 |\n| Table 4. | Performance Metrics for Continuous Processes..........................................................................26 |\n| Table 5. | Performance Metrics for Discrete Processes...............................................................................26 |\n| Table 6. | Metrics for Measuring System Performance ...............................................................................27 |\n| Table 7. | Nominal System Properties for Measuring System Performance................................................27 |\n| Table 8. | Metrics for Measuring Network Performance.............................................................................28 |\n| Table 9. | ISA/IEC-62443-3-3 Requirements to Security Level Mapping......................................................29 |\n| Table 10. | Metrics Types Collected from the TE Simulation .......................................................................35 |\n| Table 11. | Listing of the METRICS Table in the Results Database...............................................................36 |\n\n## Table of Figures\n\n| Figure 1."}], "metadata": {"source": "An Industrial Control System Cybersecurity Performance Testbed", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n3.2.1, Appendix F. 3.2.11 |\n| DP-3: Detection processes are tested. 3.2.1, CP-2, CP-3, IR-3, IR-8 NIST SP 800-53 Rev."}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Using Business Impact Analysis to Inform Risk Prioritization and Response:\n\nThe use of a common methodology also supports enterprise communication and collaboration to better understand what constitutes sensitivity and criticality in each enterprise's unique context. An example of such a methodology is described in the Criticality Analysis Process Model [NISTIR8179]. This model includes top-down and bottom-up analyses that connect different levels of the enterprise to support consistent and comprehensive assessments. NIST IR 8179 uses the term 'baseline criticality . ' These concepts are used in Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations , NIST Special Publication (SP) 800161 Revision 1 [SP800-161R1], and defined as,\n\n| Publication Identifier | Date | Type of Edit | Change | Location |\n|--------------------------|------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------|\n| NIST IR 8286D-upd1 | 02/26/2025 | Editorial | Added NIST IR 8286D to the list of IR 8286 series publications | Sec. 1 (p. 3) |\n| NIST IR 8286D-upd1 | 02/26/2025 | Editorial | Updated quotes from NIST IR 8286A to reflect the content of NIST IR 8286Ar1-ipd | Sec. 1 (p. 4) |\n| NIST IR 8286D-upd1 | 02/26/2025 | Editorial | Added reference to the new change log | Sec. 1.3 (p. 5) |\n| NIST IR 8286D-upd1 | 02/26/2025 | Editorial | Updated footnote 8 to specify the correct section number from NIST IR 8286C r1-ipd | Sec. 2.2 (p."}], "metadata": {"source": "Using Business Impact Analysis to Inform Risk Prioritization and Response", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to 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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Risk Management for Replication Devices:\n\nInspect the device for defects, delivery errors (e.g., wrong version), and malware before accepting delivery. Once acquired, include networked/wireless RDs and those with nonvolatile storage in the associated system security plan. Document device information, supply chain (e.g., distributer) information, default and customized configuration settings, security/usage policies, and any other information related to the acquisition and security requirements of the device.\n\nNational Institute of Standards and Technology, Special Publication 800-161, Supply Chain Risk Management Practices for Federal Information Systems and Organizations . http://csrc.nist.gov/publications/drafts/800161/sp800\\_161\\_2nd\\_draft.pdf"}], "metadata": {"source": "Risk Management for Replication Devices", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations provide? (Part 4)"}, {"role": "assistant", "content": "to review all draft publications during public comment periods and provide feedback to NIST. All NIST publications, other than the ones noted above, are available at http://csrc.nist.gov/publications.\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930 Electronic mail: 800-137comments@nist.gov\n\n\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\\_\n\n## Acknowledgements\n\nThe authors, Kelley Dempsey, Arnold Johnson, Matthew Scholl and Kevin Stine of the National Institute of Standards and Technology (NIST), Ronald Johnston of the Department of Defense Chief Information Officer, Defense-wide Information Assurance Program (DOD-CIO, DIAP), Alicia Clay Jones and Angela Orebaugh of Booz Allen Hamilton, and Nirali Shah Chawla of PricewaterhouseCoopers LLP (PwC), wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. The authors would like to acknowledge their colleagues for their keen and insightful assistance with technical issues throughout the development of the document. And finally, the authors gratefully acknowledge and appreciate the significant contributions from individuals and organizations in the public and private sectors whose thoughtful and constructive comments improved the overall quality and usefulness of this publication."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 System and Network Security Acronyms and Abbreviations:\n\n| automatic identification and data capture | | AIM | Association for Automatic Identification and Mobility | | AIT | automatic identification technology | | AJAX | Asynchronous JavaScript and XML | | AK | authorization key | | AKID | authorization key identifier | | AKM | authentication and key management | | ALG | application layer gateway | | ANSI | American National Standards Institute | | AP | access point | | API | application programming interface |"}], "metadata": {"source": "System and Network Security Acronyms and Abbreviations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Federal Information and Information Systems:\n\nThe minimum security requirements cover seventeen security-related areas with regard to protecting the confidentiality, integrity, and availability of federal information systems and the information processed, stored, and transmitted by those systems. The security-related areas include: (i) access control; (ii) awareness and training; (iii) audit and accountability; (iv) certification, accreditation, and security assessments; (v) configuration management; (vi) contingency planning; (vii) identification and authentication; (viii) incident response; (ix) maintenance; (x) media protection; (xi) physical and environmental protection; (xii) planning; (xiii) personnel security; (xiv) risk assessment; (xv) systems and services acquisition; (xvi) system and communications protection; and (xvii) system and information integrity. The seventeen areas represent a broad-based, balanced information security program that addresses the management, operational, and technical aspects of protecting federal information and information systems.\n\nIdentification and Authentication (IA): Organizations must identify information system users, processes acting on behalf of users, or devices and authenticate (or verify) the identities of those users, processes, or devices, as a prerequisite to allowing access to organizational information systems.\n\nAUTHENTICATION: Verifying the identity of a user, process, or device, often as a prerequisite to allowing access to resources in an information system."}], "metadata": {"source": "Minimum Security Requirements for Federal Information and 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 Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines provide? (Part 5)"}, {"role": "assistant", "content": "osure Notice\n\nNOTICE: ITL has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL.\nHowever, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Table of Contents\n\n| Executive Summary............................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Software Supply Chain (SSC) -Definition and Model .....................................................................4 |\n| 2.4.1. Software Supply Chain Defects ....................................................................................................6 |\n| 2.4.2. Software Supply Chain Attacks.....................................................................................................6 |\n| SSC Security -Risk Factors and Mitigation Measures .....................................................................8 |\n| 3. |\n| 3.1.1."}], "metadata": {"source": "Strategies for the Integration of Software Supply Chain Security in DevSecOps CI_CD Pipelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Computer Security Division 2003 Annual Report:\n\nF or many years, the Computer Security Division has made great contributions to help secure our nation's sensitive information and information systems. Our work has paralleled the evolution of IT , initially focused principally on mainframe computers, to now encompass today's wide gamut of information technology devices. Our important responsibilities were re-affirmed by Congress with passage of the Federal Information Security Management Act (FISMA) of 2002 and the Cyber Security Research and Development Act of 2002.\n\nOur key 2003 accomplishments include advancing development of our cryptographic standards toolkit, our E-authentication work, our management and technical security guidelines, and expanding our Cryptographic Module Validation Program. Our research efforts include advancing development of (1) better means of access controls, (2) means to secure personal digital assistants, and (3) specifications to promote smart card\n\ndifferent engineering disciplines, computer programming, systems analysis, and mathematics; management positions; information technology auditing; legal experience (two Board members are attorneys); an extensive history of professional publications; and professional journalism. Members have worked (and in many cases, are continuing to work in their full time jobs) on the development and evolution of some of the most important pieces of information security and privacy in the Federal Government, including the Privacy Act of 1974, the Computer Security Act of 1987, the Federal Public Key Infrastructure (PKI) effort, and numerous e-Government services and initiatives."}], "metadata": {"source": "Computer Security Division 2003 Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Control Baselines for Information Systems and Organizations:\n\nSee [SP 800-37], Task S-2, Control Tailoring, for additional guidance on tailoring control baselines for systems and environments of operation.' | 9 | | 12-10-2020 | Editorial | Section 2.4 (Footnote 28): Change 'Guidance on developing privacy plans is forthcoming.' to 'Guidance on developing privacy and supply chain risk management plans is forthcoming.' | 9 | | 12-10-2020 | Editorial | Table 3-1 (AC-3(1)) Title: Change 'FUNCTION' to 'FUNCTIONS' | 16 | | 12-10-2020 | Editorial | Table 3-1 (AC-3(6)): Change 'MP-4, SC-28' to 'MP-4 and SC-28' | 16 | | 12-10-2020 | Editorial | Table 3-1 (AC-13): Change 'AC-2, AU-6' to 'AC-2 and AU-6' | 18 | | 12-10-2020 | Editorial | Table 3-1 (AC-19(5)) Title: Change 'FULL DEVICE AND' to 'FULL DEVICE OR' | 19 | | 12-10-2020 | Editorial | Table 3-1 (AC-20(4)) Title: Change 'NETWORK-ACCESSIBLE' to 'NETWORK ACCESSIBLE' | 19 | | 12-10-2020 | Editorial | Table 3-2 (AT-3(5)) Title: Change 'ACCESSING PERSONALLY' to 'PROCESSING PERSONALLY' | 20 | | 12-10-2020 | Editorial | Table 3-3 (AU-7(2)) Title: Change 'SEARCH AND SORT' to 'SORT AND SEARCH' | 21 | | 12-10-2020 | Editorial | Table 3-3 (AU-15): Change 'Incorporated into' to 'Moved to' | 22 |"}], "metadata": {"source": "Control Baselines for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Stateless Hash-Based Digital Signature Standard:\n\nThis standard specifies the stateless hash-based digital signature algorithm (SLH-DSA). Digital signatures are used to detect unauthorized modifications to data and to authenticate the identity of the signatory. In addition, the recipient of signed data can use a digital signature as evidence in demonstrating to a third party that the signature was, in fact, generated by the claimed signatory. This is known as non-repudiation since the signatory cannot easily repudiate the signature at a later time. SLH-DSA is based on SPHINCS + , which was selected for standardization as part of the NIST Post-Quantum Cryptography Standardization process. 1. Name of Standard. Stateless Hash-Based Digital Signature Standard (FIPS 205). 2. Category of Standard. Computer Security. Subcategory. Cryptography. 3. Explanation. This standard specifies a stateless hash-based digital signature scheme (SLHDSA) for applications that require a digital signature rather than a written signature. Additional digital signature schemes are specified and approved in other NIST Special Publications and FIPS publications (e.g., FIPS 186-5 [1]). A digital signature is represented in a computer as a string of bits and computed using a set of rules and parameters that allow the identity of the signatory and the integrity of the data to be verified. Digital signatures may be generated on both stored and transmitted data. 7. Applications. A digital signature algorithm allows an entity to authenticate the integrity of signed data and the identity of the signatory. The recipient of a signed message can use a digital signature as evidence in demonstrating to a third party that the signature was, in fact, generated by the claimed signatory. This is known as non-repudiation since the signatory cannot easily repudiate the signature at a later time."}], "metadata": {"source": "Stateless Hash-Based Digital Signature Standard", "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 Guidelines for Smart Grid Cybersecurity:\n\nImpact Levels .......................................................... 76\nImpact Levels for the CI&A Categories ......................................................................................\n77\n3.3\n3.4 Selection of Security Requirements ............................................................................................. 79\n3.5 Security Requirements Example .................................................................................................. 80\n3.6 Recommended Security Requirements ........................................................................................ 81\n3.7 Access Control (SG.AC) ............................................................................................................. 93\n3.8 Awareness and Training (SG.AT) ............................................................................................. 107\n3.9 Audit and Accountability (SG.AU) ........................................................................................... 111\n3.10 Security Assessment and Authorization (SG.CA) ..................................................................... 120\n3.11 Configuration Management (SG.CM) ....................................................................................... 124\n3.12 Continuity of Operations (SG.CP) ............................................................................................. 132\n3.13 Identification and Authentication (SG.IA) ................................................................................ 139\n3.14 Information and Document Management (SG.ID) .................................................................... 142\n3.15 Incident Response (SG.IR) ........................................................................................................ 146\n3.16 Smart Grid Information System Development and Maintenance (SG.MA) .............................."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case:\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\nComputer security; Cybersecurity Framework (CSF); distributed control systems (DCS); industrial control systems (ICS); information security; manufacturing; network security; programmable logic controllers (PLC); risk management; security controls; supervisory control and data acquisition (SCADA) systems.\n\nThe Executive Order 13636, 'Improving Critical Infrastructure Cybersecurity,' [1] directed the development of the voluntary Cybersecurity Framework that provides a prioritized, flexible, repeatable, performance-based, and cost-effective approach to manage cybersecurity risk [1] for those processes, information, and systems directly involved in the delivery of critical infrastructure services."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Guidance for First Responder Mobile and Wearable Devices:\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- Section 2 provides an overview of the technology analyzed,\n- Section 3 outlines the methodology used for analysis\n- Section 4 summarizes the test plan and findings\n- Section 5 suggests best practices and guidance for public safety mobile and wearable devices\n- Section 6 concludes the document with a review of the document, future considerations, and other related NIST work\n- Section 7 contains a list of references used in the development of this document"}], "metadata": {"source": "Security Guidance for First Responder Mobile and Wearable Devices", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI):\n\n| 1. INTRODUCTION ..........................................................................................................................."}], "metadata": {"source": "Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)", "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 Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms:\n\nasymmetric-key algorithm; identity authentication; confidentiality; digital signatures; encryption; integrity; key establishment; message authentication; random bit generation; symmetric-key algorithm."}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Cryptographic Mechanisms", "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 High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture provide? (Part 4)"}, {"role": "assistant", "content": "ble at https://csrc.nist.gov/pubs/sp/800/223/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA).\n## Abstract\n\nSecurity is essential component of high-performance computing (HPC). HPC systems often differ based on the evolution of their system designs, the applications they run, and the missions they support. An HPC system may also have its own unique security requirements, follow different security guidance, and require tailored security solutions. Their complexity and uniqueness impede the sharing of security solutions and knowledge. This NIST Special Publication aims to standardize and facilitate the information and knowledge-sharing of HPC security using an HPC system reference architecture and key components as the basis of an HPC system lexicon. This publication also analyzes HPC threats, considers current HPC security postures and challenges, and makes best-practice recommendations. ## Keywords\n\nhigh-performance computing; HPC reference architecture; HPC security; HPC security posture; HPC threat analysis; security guidance. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP):\n\n| title: \"Apple macOS 11 (Big Sur) Test Baseline\" description: | This guide describes the prudent actions to take when securing a system against the Test Baseline. authors: | |=== |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| profile: |\n| - section: \"Authentication\" rules: - auth_pam_login_smartcard_enforce - auth_pam_su_smartcard_enforce - auth_pam_sudo_smartcard_enforce - auth_smartcard_allow - section: \"Auditing\" rules: - audit_acls_files_configure - audit_acls_files_mode_configure - audit_acls_folder_wheel_configure |\n\n- audit - OpenBSM 3\n- auth - Smartcard authentication\n- icloud - Apple's iCloud/Apple ID service\n- os - Rules to configure the operating system that do not fit into the other categories\n- pwpolicy - Password policy\n- system\\_settings or sysprefs - Settings controlled within the System Settings or System Preferences application\n\n```\ntitle: \"Limit SSHD to FIPS 140 Validated Ciphers\" discussion: | If SSHD is enabled, then it _MUST_ be configured to limit the ciphers to algorithms that are FIPS 140-validated. FIPS 140-2 is the current standard for validating that mechanisms used to access cryptographic modules utilize authentication that meets federal requirements. Operating systems utilizing encryption _MUST_ use FIPS-validated mechanisms for authenticating to cryptographic modules."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.1 (NIST 3.4.1)?"}, {"role": "assistant", "content": "According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance):\n\n3.4.1 2. 3.4.1 2. 3.4.1 2."}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "cmmc_level": "all", "nist_control": "3.4.1", "cmmc_practice_id": "CM.L2-3.4.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI) provide? (Part 2)"}, {"role": "assistant", "content": "he requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A-130, Appendix IV: Analysis of Key Sections .\nSupplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## National Institute of Standards and Technology Special Publication 800-79-2\n\nNatl. Inst. Stand. Technol. Spec. Publ. 800-79-2, 120 pages (July 2015) http://dx.doi.org/10.6028/NIST.SP.800-79-2 CODEN: NSPUE2\n\nThis publication is available free of charge from:\n\nhttp://dx.doi.org/10.6028/NIST.SP.800-79-2\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to A Security Perspective on the Web3 Paradigm:\n\nugh smartphones, organizations had access to a myriad of sensor data, geolocation data, contact information, and stored media, all of which was made accessible through application permission requests.\nAs organizations continued to expand and collect user data, they also began to diversify their offerings. Many opened online storefronts that allowed users to purchase licenses to view digital media, such as music, books, and films. 1 Users could not easily migrate away from individual platforms since their licenses were specific to that platform. Some users found out too late that if they were removed from an organization's platform, they lost all access to the media for which they had purchased licenses [6]. In many cases, users were unable to return digital content that they were unhappy with or transfer digital content to other users (either a temporary transfer, such as lending to another user, or a permanent transfer, such as selling a digital item to another user). This change from the ownership of physical items to licenses to view digital content was seen by many as a step backwards. Proponents of Web3 saw the mass collection of user data, platform lock-in, and the inability to obtain and transfer the ownership of digital items as issues with Web 2.0."}], "metadata": {"source": "A Security Perspective on the Web3 Paradigm", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Computer Security Division 2009 Annual Report:\n\n| 33 33 | 33 33 | | | | Automated Combinatorial Testing for Software | | | | | 11 | Conformance Verification for Access Control | 34 | 34 | | Small and Medium Size Business Outreach | | Policies Forensics forWeb Services | 35 | 35 | | Health Information Technology Security | 11 | Mobile Handheld Device Security and Forensics | 35 | 35 | | | 12 | | | | | Smart Grid Cyber Security | 13 | NIST Cloud Computing Project Policy Machine | 36 36 | 36 36 | | Supply Chain Risk Management | 13 | Security for Grid and Pervasive Systems | 38 | 38 | | Cryptographic Validation Programs and Laboratory Accreditation | 14 14 | Security Ontologies: Modeling Quantitative Risk Analysis | | | | Laboratory Accreditation Cryptographic ModuleValidation Program and Cryptographic | | of Enterprise Systems | 38 | 38 | | Algorithm Validation Program | 15 16 | Automated Vulnerability Management National Vulnerability Database | 39 39 | 39 39 | | Automated Security Testing andTest Suite Development ISO Standardization of Cryptographic ModuleTesting | 18 18 | Security Content Automation Protocol | 39 | 39 |"}], "metadata": {"source": "Computer Security Division 2009 Annual Report", "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 is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 1_ Overview:\n\n3.3.3 Using Security Capabilities in Security Control Assessment ... 3.3.3 Using Security Capabilities in Security Control Assessment\n\nWhile the term security capability is defined in SP 800-53, no specific capabilities are identified, allowing organizations to define security capabilities according to security goals."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "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 Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols provide? (Part 5)"}, {"role": "assistant", "content": "results of this project include a set of specifications that include security services, protocols and mechanisms for protecting user data in networks that are based on the OSI computer network model.\nProductive security services that protect user data are specified and supportive security services, such as key management and access control, are also provided. No cryptographic algorithms are included in these specifications. NIST is working with NSA and industry to identify and develop a framework of base standards for network security. In 1989, NIST established the OSI Security Laboratory where interested researchers from government and industry develop and demonstrate new ideas in network security. The major goals of NIST's network security activities are to:\n\n- Identify and develop 'security standards for open systems\n- Specify a key management system that supports these security standards\n- Encourage the development of interoperable equipment\n\ni'\n\ni:\n\nr<\n\n<11\n\n'\n\nV-\n\n'\n\n.'T.^.X v. ^1\n\n'\n\n'\n\n-\n\n». *\n\n^\n\nL':\n\nJ\n\n6»\n\n•*»•!:•\n\n».:c s-\n\n.e trWOe\n\n'i>sfi5^\n\n'^9\n\nj^;,\n\n4 ':'\n\n'v;\n\nv ,; k*^t\n\nE\n\n^\"<1^\n\ns* * ^'f\n\n'\n\n4'3\n\n'{Loti\n\n{1.0*5\n\n, 7'.^!::?^\n\n1\n\n*\n\n?U>\n\n.'?*'^6\n\nn'^\n\n''\n\nbfTti iSr*\n\n'\n\nsT\".p\n\n-j, i':tvV\n\n,-\n\n.,\n\n,:\n\nbf^f^\n\n/ti\n\n::^0f.ri^'il^^7K'o-\n\n«'\n\nr Juxv'i'ii$> ,\n\n-^s'\n\n'=•''' I\n\n19 . ^oO\n\n:r'^^\n\n\\*;ti:;i,*'x i'\n\n^' TSiI'A\n\nsf XC-^Q\n\n^ Er\n\nX*;n,?v^'CV^\n\n.'[i^QlXir^ftiit^\n\n.[i^Qiziz^qtt v-'itiv#'! l&^£SmUl^tip'll\n\n(XSiOCU)\n\ntpffT\n\no\"? ^sbodjnji palrisxXc!>i'? paxnsxxc^\n\nIPI\n\n,.:tos-tc!itq i«i?^*x'9naios^\n\nbftjs\n\n67j»\n\nu\n\nrt:rivj>#p\n\nX4AO'li#fi>nri:s:*'nI\n\nbfijs\n\nU'*\n\nf-.4. io\n\n:^Ai»itn'^vox<\n\nXAnai^ilV, ainaantiboL\n\nfUKxtu^v i#o\n\n'i-V'.f\n\n@- timc^i:^$s%f\n\n^dsi- ^\n\n^\n\nfi«? •\n\n*i'\n\n,\n\nui&.^ijj-.*5ti\n\n^*«il-l'\n\nJ«3Si»r..n;\n\nfoi-*fe io\n\n:io\n\n!IP\n\n«b7tf:»bfi4^5i\n\n-pii\n\n9u:ic^s0%\n\nft/r^ xA\n\niAO'ist y#i|\n\n6 -\" 6\n\n-f.bl\n\n-aroenoga\n\n%f i ia%f\n\n:\n\n:?"}], "metadata": {"source": "Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data:\n\n- [ 0] swapper/0 (struct addr:ffffffff81e13500) - [ 1] systemd (struct addr:ffff88007c460000) - [ 2] kthreadd (struct addr:ffff88007c460e00) - [ 3] ksoftirqd/0 (struct addr:ffff88007c461c00) - [ 4] kworker/0:0 (struct addr:ffff88007c462a00) - [ 5] kworker/0:0H (struct addr:ffff88007c463800) - [ 6] kworker/u2:0 (struct addr:ffff88007c464600) - [ 7] rcu\\_sched (struct addr:ffff88007c465400) - [ 8] rcu\\_bh (struct addr:ffff88007c466200) - [ 9] migration/0 (struct addr:ffff88007c467000) - [ 10] watchdog/0 (struct addr:ffff88007c4c8000) - [ 11] kdevtmpfs (struct addr:ffff88007c4c8e00) - [ 12] netns (struct addr:ffff88007c4c9c00) - [ 13] perf (struct addr:ffff88007c4caa00) - [ 14] xenwatch (struct addr:ffff88007c4cb800) - [ 15] xenbus (struct addr:ffff88007c4cc600) - [ 16] khungtaskd (struct addr:ffff88007c4cd400) - [ 17] writeback (struct addr:ffff88007c4ce200) - [ 18] ksmd (struct addr:ffff88007c4cf000) - [ 19] crypto (struct addr:ffff88007c568000) - [ 20] kintegrityd (struct addr:ffff88007c568e00) - [ 21] bioset (struct addr:ffff88007c569c00) - [ 22] kblockd (struct addr:ffff88007c56aa00) - [ 23] ata\\_sff (struct addr:ffff88007c56b800) - [ 24] md (struct addr:ffff88007c56c600) - [ 25] devfreq\\_wq (struct addr:ffff88007c56d400) - [ 26] kworker/0:1 (struct addr:ffff88007c56e200) - [ 27] kworker/u2:1 (struct addr:ffff88007c56f000) - [ 29] kswapd0 (struct addr:ffff880076060e00) - [ 30] vmstat (struct addr:ffff880076061c00) - [ 31] fsnotify\\_mark (struct addr:ffff880076062a00) - [ 32] ecryptfs-kthrea (struct addr:ffff880076063800) - [ 48] kthrotld (struct addr:ffff880076131c00) - ["}], "metadata": {"source": "A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data", "cmmc_level": "1", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security Architecture Design Process for Health Information Exchanges (HIEs):\n\n|\n| Federal Regulations: Initial Set of Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology, 45 CFR Part 170 (Interim Final Rule) | Eligible professionals and eligible hospitals under the Medicare and Medicaid EHR Incentive Programs | Risk Assessment; Secured Communication Channel; Document Confidentiality; Manage Consent Directives | The interim final rule became effective February 12, 2010. It adopts an initial set of standards, implementation specifications, and certification criteria, as required by section 3004(b)(1) of the Public Health Service Act. It represents the first step in an incremental approach to adopting standards, implementation specifications, and certification criteria to enhance the interoperability, functionality, utility, and security of health information technology and to support its meaningful use. |\n| Federal Regulations: Protection of Human Subjects, 45 CFR Part 46 ('The Common Rule' for Human Subjects Protection) | Any institution conducting research involving human subjects conducted, supported, or otherwise subject to regulation by any federal department or agency | Risk Assessment; Document Confidentiality; Manage Consent Directives; De- Identification | Requires consent of research subjects, subject to some exemptions, including research on records where if the information is recorded by the investigator in such a manner that subjects cannot be identified, directly or through identifiers linked to the subjects. Consent forms must include notice of adequate provisions to protect the privacy of subjects and to maintain the confidentiality of data."}], "metadata": {"source": "Security Architecture Design Process for Health Information Exchanges (HIEs)", "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 Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\n\nauthentication; FIPS 201; identity credential; logical access control; on-card biometric comparison; Personal Identity Verification (PIV); physical access control; smart cards; secure messaging. 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. Homeland Security Presidential Directive-12 (HSPD-12) called for the adoption of a common identification standard to govern the interoperable use of identity credentials to allow physical and logical access to federally controlled facilities and information systems. In response, Federal Information Processing Standard (FIPS) 201 [FIPS201], Personal Identity Verification (PIV) of Federal Employees and Contractors , was developed to define reliable, government-wide identity credentials for use in applications such as access to federally controlled facilities and information systems. FIPS 201 supports multiple types of authenticators, including authenticators on smart cards (also known as PIV Cards) and derived PIV credential authenticators in various other form factors. This publication contains technical specifications to interface with PIV Cards to retrieve and use identity credentials."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Reference Architecture:\n\ncivil litigation; criminal investigation; cybersecurity; digital forensics; enterprise architecture; enterprise operations; forensic readiness; incident response.\n\nNew methodologies are needed to identify, acquire, preserve, examine, and interpret digital evidence in multi-tenant cloud environments with rapid provisioning, global elasticity, and broad network accessibility. These methodologies will provide capabilities for incident response, secure internal enterprise operations, and support for the criminal justice and civil litigation systems.\n\nThe NIST Cloud Computing Forensic Science Working Group (NCC FSWG) was established to research forensic science challenges and architectures related to the cloud environment. It previously published NIST Interagency Report (IR) 8006, NIST Cloud Computing Forensic Science Challenges [1], which highlighted the unique digital forensic challenges of public cloud computing services under three aspects of operation: normal operations, adverse operations (i.e., when cloud computing resources are under attack), and operations during criminal exploitation. A description and discussion of digital forensics in cloud computing is provided in Section 1.1."}], "metadata": {"source": "NIST Cloud Computing Forensic Reference 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 does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements:\n\nThis report defines the requirements and associated test procedures necessary for products or modules to achieve one or more Security Content Automation Protocol (SCAP) validations. Validation is awarded based on a defined set of SCAP capabilities by independent laboratories that have been accredited for SCAP testing by the NIST National Voluntary Laboratory Accreditation Program (NVLAP). This publication is intended for NVLAP accredited laboratories conducting SCAP product and module testing for the program, vendors interested in receiving SCAP validation for their products or modules, and organizations deploying SCAP products in their environments. Accredited laboratories use the information in this report to guide their testing and ensure all necessary requirements are met by a product before recommending to NIST that the product be awarded the requested validation. Vendors may use the information in this report to understand the features that products and modules need to be considered for SCAP validation. Government agencies and integrators use the information to gain insight into the criteria required for SCAP validated products. The secondary audience for this publication includes end users, who can review the test requirements to understand the capabilities of SCAP validated products and gain knowledge about SCAP validation. The National Institute of Standards and Technology (NIST) Security Content Automation Protocol (SCAP) Validation Program tests the ability of products and modules to use the features and functionality available through SCAP and its components. SCAP 1.3 consists of a suite of specifications for standardizing the format and nomenclature by which security software communicates information about software flaws and security configurations. The standardization of security information facilitates interoperability and enables predictable results among disparate SCAP enabled security software."}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1 support CMMC certification?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1:\n\n\n\n## The Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.1\n\n## Recommendations of the National Institute of Standards and Technology\n\nDavid Waltermire Stephen Quinn Karen Scarfone\n\nNIST Special Publication 800-126 Revision 1\n\nThe Technical Specification for the Security Content Automation Protocol (SCAP): SCAP Version 1.1\n\nRecommendations of the National Institute of Standards and Technology\n\nDavid Waltermire Stephen Quinn Karen Scarfone\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nFebruary 2011\n\n\n\nU.S. Department of Commerce\n\nGary Locke, Secretary\n\nNational Institute of Standards and Technology\n\nDr. Patrick D. Gallagher, Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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. National Institute of Standards and Technology Special Publication 800-126, Revision 1 39 pages (Feb."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program:\n\n..................................................8 |\n| 2.4.5.\nOther Roles...................................................................................................................................8 |\n| 2.7.1. Organizational Considerations ...................................................................................................11 |\n| 2.7.2. Manageability.............................................................................................................................11 |\n| 2.7.3. Data Management Concerns......................................................................................................11 |\n| 3. Workflow for Implementing an Information Security Measurement Program ................................12 |\n| 3.1.1. Gathering Stakeholder Input......................................................................................................14 |\n| 3.1.2. Goals and Objectives..................................................................................................................14 3.1.3."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\nManufacturing industries are usually located within a confined factory or plant-centric area. Communications in manufacturing industries are typically performed using fieldbus and local area network (LAN) technologies that are reliable and high speed. Wireless networking technologies are gaining popularity in manufacturing industries. Fieldbus includes, for example, DeviceNet, Modbus, and Controller Area Network (CAN) bus."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Information Security Guide for Government Executives provide? (Part 4)"}, {"role": "assistant", "content": "ides a broad overview of information security program concepts to assist senior leaders in understanding how to oversee and support the development and implementation of information security programs.\nSenior management is responsible for:\n\n- Establishing the organization's information security program;\n- Setting program goals and priorities that support the mission of the organization; and\n- Making sure resources are available to support the information security program and make it successful. Senior leadership commitment to information security is more important now than ever before. Studies have shown that senior management's commitment to information security initiatives is the single most critical element that impacts an information security program's success. Organizational assets and operations have become increasingly dependent on information and technology to accomplish mission and performance goals. Recognizing this dependency, information becomes a strategic enabler for mission accomplishment; therefore, protecting that information becomes a high priority of an organization. Meeting this need necessitates senior leadership focus on effective information security governance and support, which requires integration of security into the strategic and daily operations of an organization. When considering this challenge, several key security questions emerge for the executive. This document will answers these questions and provides strategies to aid senior leaders in implementing an effective information security program. 1. Why do I need to invest in information security? 2. Where do I need to focus my attention in accomplishing critical information security goals? 3. What are the key activities to build an effective information security program? 4. What are the information security laws, regulations, standards, and guidance that I need to understand to build an effective security program? 5."}], "metadata": {"source": "Information Security Guide for Government Executives", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Automation Support for Security Control Assessments_ Software Asset Management provide? (Part 5)"}, {"role": "assistant", "content": "Software Asset Management (SWAM) Capability Definition, Overview, and Scope.........3 | | 2.1 SWAM Capability Description ...............................................................................................3 | | 2.2 SWAM Attack Scenarios and Desired Result..........................................................................7 | | 2.3 Assessment Objects Protected and Assessed by SWAM.........................................................9 | | 2.4 Example SWAM Data Requirements ....................................................................................14 | | 2.5 SWAM Concept of Operational Implementation ..................................................................16 | | 2.5.1 Collect Actual State.........................................................................................................16 | | 2.5.2 Collect Desired State ......................................................................................................17 | | 2.5.3 Find/Prioritize Defects....................................................................................................18 | | 2.6 SP 800-53 Control Items that Support SWAM .....................................................................18 | | 2.6.1 Process for Identifying Needed Controls........................................................................18 | | 2.6.2 Control Item Nomenclature ............................................................................................19 | | 2.7 SWAM Specific Roles and Responsibilities ..........................................................................20 | | 2.8 SWAM Assessment Boundary ...............................................................................................22 | | 2.9 SWAM Actual State and Desired State Specification ...........................................................22 | | 2.10 SWAM Authorization Boundary and Inheritance...............................................................23 | | 2.12 SWAM Assessment Criteria Device Groupings to Consider | | 2.11 SWAM Assessment Criteria Recommended Scores and Risk-Acceptance Thresholds.......23 | | ..............................................23 | | 3.1 Introduction and Steps for Adapting This Plan....................................................................24 | | 3.1.1 Select Defect Checks to Automate...................................................................................24 | | 3.1.3 Automate Selected Defect Checks...................................................................................26 | | 3.2 SWAM Sub-Capabilities and Defect Check Tables and Templates......................................27 | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 3.2.1 Foundational Sub-Capabilities and Corresponding Defect"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Storage Encryption Technologies for End User Devices:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guide to Storage Encryption Technologies for End User Devices", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols:\n\nnated with another SNICP at an intermediate system, then the data origin authentication is supplied by a combination of key management and explicit protection of source and destination NSAP addresses.\nThis protocol can support the access control service described in ISO 7498/2 using security labeling and using attributes associated with cryptographic keys. This protocol can support the peer entity authentication and data origin authentication services described in ISO 7498/2 using attributes associated with cryptographic keys."}], "metadata": {"source": "Secure Data Network Systems (SDNS) Network, Transport, and Message Security Protocols", "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 COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0:\n\n| TABLE | PAGE | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| | TABLE 3.2-1 - SECURITY ASSUMPTIONS - TOE.....................................................................................................................7 | | | TABLE 3.2-2 - SECURITY ASSUMPTIONS - PERSONNEL..........................................................................................................7 | | | TABLE 3.3-1 - SECURITY POLICIES........................................................................................................................................8 | | | TABLE 3.4-1 - SECURITY THREATS ADDRESSED BY TOE'S ENVIRONMENT ........................................................................11 | | | TABLE 3.4-2 - SECURITY THREATS ADDRESSED BY TOE....................................................................................................12 | | | TABLE 3.4-3 - SECURITY THREATS ADDRESSED JOINTLY BY TOE AND ENVIRONMENT .....................................................13 | | | TABLE 4-1 - ENVIRONMENTAL SECURITY OBJECTIVES ......................................................................................................22 | | | TABLE 4-2 - TOE SECURITY OBJECTIVES ..........................................................................................................................25 | | | TABLE 4-3 - JOINT TOE/ENVIRONMENT SECURITY OBJECTIVES ........................................................................................27 | | | TABLE 5-1 - FUNCTIONAL COMPONENTS - TOE.................................................................................................................29 | | | TABLE 5-2 - FUNCTIONAL COMPONENTS - IT ENVIRONMENT ............................................................................................34 | | | TABLE 5-3 - SOF METRICS - TOE......................................................................................................................................36 | | | TABLE 5-4 - SOF METRICS - IT ENVIRONMENT.................................................................................................................38 | | | TABLE 6-1 - EAL-CSPP ASSURANCE COMPONENTS..........................................................................................................39 | | | TABLE 6-2 - EAL-CSPP AUGMENTATION TO EAL-2 .........................................................................................................40 | |"}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "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 Guidelines on PDA Forensics:\n\nnciples aim to ensure the integrity and accountability of digital evidence through its entire life cycle. Proper handling of evidence is always vital for it to be admissible in judicial proceedings.\nHowever, different standards may apply to different types of investigations. The degree of training and expertise required to execute a forensic task largely depends on the level of evidence required in the case [Pur]."}], "metadata": {"source": "Guidelines on PDA Forensics", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\n\n5 |\n| | 3.2 The Chain of Trust | (CoT)................................................................................ 6 |\n| | 3.3 | Supply Chain Protection ................................................................................."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\n3.1.4. 3.1.4 DEFINE SAMPLE POPULATIONS\n\nOrganizations may find that collecting data from every object of every system within an organization may be impractical or cost-prohibitive."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "nist_control": "3.1.4", "cmmc_practice_id": "AC.L2-3.1.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Guide to Cyber Threat Information Sharing:\n\n3.3.2 of NIST Special Publication 800-61 [1]."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "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 is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology:\n\n3.5.2 Maintenance Plans for Scenario 2, Emergency Patching... 3.5.2 Maintenance Plans for Scenario 2, Emergency Patching\n\nOrganizations should consider using the same general approach for emergency patching as for routine patching, except with a highly accelerated schedule."}], "metadata": {"source": "Guide to Enterprise Patch Management Planning_ Preventive Maintenance for Technology", "cmmc_level": "all", "nist_control": "3.5.2", "cmmc_practice_id": "IA.L2-3.5.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Case Studies in Cyber Supply Chain Risk Management_ Anonymous Consumer Electronics Company provide? (Part 5)"}, {"role": "assistant", "content": "ort potential risks to leadership. The information security team enforces the principle of least privilege, and the user base has historically been enthusiastic about new security tools and processes.\n## Supplier Management\n\n## Key Aspects of Managing Supplier Relationships\n\nStrong supplier relationships are a core element of the Consumer Electronics Company's supply chain management. The company deliberately fosters formal and personal relationships with all partners and suppliers and has worked with some suppliers for over a decade. This personal approach helps build a better mutual understanding of each business and strong trust over time. To maintain these relationships, the company's employees perform informal touchpoints and attend regular on-site meetings with each supplier. These meetings occur quarterly for some critical suppliers. Relationships are managed directly by the development team responsible for the ultimate product. Whenever possible, the Consumer Electronics Company will source new components from existing suppliers to minimize complexity and strengthen existing relationships. When new vendors are required, the Global Sourcing team will perform an assessment of the new supplier's security practices. These assessments are largely driven by the company's experience with supply chain incidents, cyber hygiene best practices, and conformance with security requirements from the U.S. Customs and Border Protection's (CBP) Customs-Trade Partnership Against Terrorism i (CTPAT) program. CTPAT is the Department of Homeland Security's largest public-private partnership for supply chain risk management. The voluntary program grants the Consumer Electronics Company a low-risk customs designation for demonstrating compliance with a broad range of supply chain security assurances, including secure transit and storage, personnel controls, and IT security."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Anonymous Consumer Electronics Company", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Guidelines for Securing Radio Frequency Identification (RFID) Systems:\n\n3.1.2 | Tracking... 3.1.2 Power Source\n\nTags need power to perform functions such as sending radio signals to a reader, storing and retrieving data, and performing other computations (e. 3.1.2 Tracking\n\nTracking applications are used to identify the location of an item, or more accurately, the location of the last reader that detected the presence of the tag associated with the item."}], "metadata": {"source": "Guidelines for Securing Radio Frequency Identification (RFID) Systems", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guide to Information Technology Security Services:\n\n- ƒ Develop processes and procedures that can effectively track the myriad service agreements and the metrics that will be applied throughout the lifecycle of the many different and disparate IT security services within an organization | Types | of Services.............................................................................................................5-1 | of Services.............................................................................................................5-1 | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 5.1 | | Management Security Services ...............................................................................5-2 | | | 5.1.1 | IT Security Program Development ...............................................................5-2 | | | 5.1.2 | IT Security Policy..........................................................................................5-3 | | | 5.1.3 | Risk Management ........................................................................................5-4 | | | 5.1.4 | IT Security Architecture ................................................................................5-4 | | | 5.1.5 | Certification and Accreditation......................................................................5-4 | | | 5.1.6 | IT Security Product Evaluation.....................................................................5-5 | | 5.2 | Operational Security Services..................................................................................5-6 | Operational Security Services..................................................................................5-6 | | | 5.2.1 | Contingency Planning ..................................................................................5-6 | | | 5.2.2 | Incident Handling..........................................................................................5-7 | | | 5.2.3 | Testing..........................................................................................................5-8 | | | 5.2.4 | Training ........................................................................................................5-9 | | 5.3 | Technical Security Services...................................................................................5-11 | Technical Security Services...................................................................................5-11 | | | 5.3.1 | Firewalls .....................................................................................................5-11 | | | 5.3.2 | Intrusion Detection .....................................................................................5-11 | | | 5.3.3 | Public Key Infrastructure ............................................................................5-12 | | Appendix A-REFERENCES.................................................................................................A-1 | Appendix A-REFERENCES.................................................................................................A-1 | Appendix A-REFERENCES.................................................................................................A-1 | | Appendix B-ACRONYM LIST..............................................................................................B-1 | Appendix B-ACRONYM LIST..............................................................................................B-1 |"}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\n| . | . | . . | III-17 |\n| III-13 | Physical/Environmental Protection-GADPS | | . | . | .\n| III-17 |\n| III-14 | Controls-GADPS | | | | | III-17 |\n| III-15 | Production, I/O Emergency, Backup, and Cont. Planning-GADPS | | | | | III-18 |\n| III-16 | Software and Maintenance-GADPS | . | . | . | . | III-18 |\n| III-17 | System Security Awareness and Training-GADPS | . | . | . | . | III-18 |\n| III-18 III-19 | Authorization and Access Controls-GADPS Audit Trail Mechanisms-GADPS | | . . | . . | . . | III-19 III-19 |\n| III-20 | Confidentiality Controls-GADPS | | | | | III-19 |\n| III-21 | Integrity Controls-GADPS | | | | | III-20 |\n| III-22 | User | Identification/Authorization-GADPS | . | . | . | III-20 |\n| III-23 | Assignment Security Responsibility-MAS | | | . | . | III-22 |\n| III-24 | Personnel Screening-MAS . | . | | . | ."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions:\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices\n\nAuthenticated Encryption, Hash, and Extendable Output Functions\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices"}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT):\n\nAlice has decided to travel outside of the United States but is diabetic and wants to monitor her blood glucose levels and receive updates on her condition from her primary care provider.\n\nAs Figure 7 shows, Alice has a wirelessenabled wearable glucose monitor and injection device (insulin pump). Blood sugar data reflecting the results of Alice's advanced diabetes treatments which are being evaluated will be published electronically and provided to her after they are processed via intelligent computing technologies. Clinicians then will proactively evaluate and personalize her treatment, sending predictive alerts for hypoglycemia and insulin dosage updates.\n\nThe GSA Headquarters Building includes over 750,000 square feet of space, two-thirds of which has been modernized. The structure incorporates a variety of smart building technologies to help its occupants work comfortably, while improving energy efficiency and achieving mandatory sustainability goals. The various technology components form an integrated automated environment (see Table 2 for an illustrative listing), that helps building and facilities managers achieve their goals of occupant satisfaction, energy use intensity, maintenance costs, water usage, and CO2 emissions."}], "metadata": {"source": "Interagency Report on the Status of International Cybersecurity Standardization for the Internet of Things (IoT)", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.2.1. 3.2.1) • Added Key History capability (Part 1, Sec."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\n- 1) Agency management should ensure that computer security has the highest level of management involvement. This involvement is also important in the computer security planning process. Computer security benefits from the multiple perspectives of and input from agency IRM, computer security, and functional, user, and applications personnel\n- 2) Agency management should identify and describe the security needs of their systems which contain sensitive information. - 3) Agency management should recognize the importance of computer security and its required planning. This recognition should be aggressively communicated to their staffs, perhaps using their computer security and awareness training programs as one of the vehicles. - 4) Agencies should incorporate computer security planning with other information systems planning activities. - 5) Agencies should consider the protection requirements for integrity and availability on an equal basis with that of confidentiality. - 6) Agencies should assess risks and select and implement realistic controls throughout the system life cycle. This involves awareness of technology changes with regard system hardware and software. This awareness also requires a knowledge of new technology and new methods for protecting and recovering from system threats. | III- 1 | Civilian Agency CSPP Distribution by Branch Government | of | of | of | of | of |\n|---------------|----------------------------------------------------------------------------|------------------------------------|--------|------|------|---------------|\n| | . | | | | . | III-4 |\n| III- 2 III- | Distribution of CSPPs by System Category Distribution of CSPPs Operational | | . | . | . . | III-6 ."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "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 Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0 provide? (Part 2)"}, {"role": "assistant", "content": "19 | List of Tables 1: Function and Category Unique Identifiers ..................................................................... 19 |\n| Table Table 2: Framework Core............................................................................................................. | 20 |\n\n## Executive Summary\n\nThe national and economic security of the United States depends on the reliable functioning of critical infrastructure. Cybersecurity threats exploit the increased complexity and connectivity of critical infrastructure systems, placing the Nation's security, economy, and public safety and health at risk. Similar to financial and reputational risk, cybersecurity risk affects a company's bottom line. It can drive up costs and impact revenue. It can harm an organization's ability to innovate and to gain and maintain customers. To better address these risks, the President issued Executive Order 13636, 'Improving Critical Infrastructure Cybersecurity,' on February 12, 2013, which established that '[i]t is the Policy of the United States to enhance the security and resilience of the Nation's critical infrastructure and to maintain a cyber environment that encourages efficiency, innovation, and economic prosperity while promoting safety, security, business confidentiality, privacy, and civil liberties.' In enacting this policy, the Executive Order calls for the development of a voluntary risk-based Cybersecurity Framework - a set of industry standards and best practices to help organizations manage cybersecurity risks. The resulting Framework, created through collaboration between government and the private sector, uses a common language to address and manage cybersecurity risk in a cost-effective way based on business needs without placing additional regulatory requirements on businesses."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Approaches for Federal Agencies to Use the Cybersecurity Framework provide? (Part 3)"}, {"role": "assistant", "content": "astructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology.\nITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nThe document highlights examples for implementing the Framework for Improving Critical Infrastructure Cybersecurity (known as the Cybersecurity Framework) in a manner that complements the use of other NIST security and privacy risk management standards, guidelines, and practices. These examples include support for an Enterprise Risk Management (ERM) approach in alignment with OMB and FISMA requirements that agency heads 'manage risk commensurate with the magnitude of harm that would result from unauthorized access, use, disclosure, disruption, modification, or destruction of a federal information system or federal information.' The use of the Cybersecurity Framework's components enable discussion about the various types of risk that might occur within federal organizations and promote conversations about how to determine the likelihood and potential consequences of risk events. These activities can then be combined with those described in NIST Special Publication (SP) 800-37, Revision 2, Risk Management Framework for Information Systems and Organizations ; SP 800-39, Managing Information Security Risk ; and other guidelines to form a comprehensive risk-based approach for security and privacy. This risk-based approach will assist agencies in determining the risks that are relevant to its mission throughout the operational lifecycle and apply an appropriate type and degree of resources to treat those risks to an acceptable level."}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Security Considerations for Code Signing:\n\nA wide range of software products (also known as code)-including firmware, operating systems, mobile applications, and application container images-must be distributed and updated in a secure and automatic way to prevent forgery and tampering. Digitally signing code provides both data integrity to prove that the code was not modified, and source authentication to identify who signed the code. This paper describes features and architectural relationships of typical code signing solutions that are widely deployed today. It defines code signing use cases and identifies some security problems that can arise when applying code signing solutions to those use cases. Finally, it provides recommendations for avoiding those problems and resources for more information. An effective and common method of protecting software is to apply a digital signature to the code. Digitally signing code provides both data integrity to prove that the code was not modified, and source authentication to identify who was in control of the code at the time it was signed. When the recipient verifies the signature, he is assured that the code came from the source that signed it, and that it has not been modified in transit. The signer is the entity responsible for managing the keys used to sign software. This role may be performed by the same organization that developed or built the software, or by an independent party in a position to vouch for the source of the code. The signer generates the code signing private/public key pair on a device that is sufficiently protected, as the security of this process relies upon the protection of the private key. In many cases, the signer then provides the public key to a certification authority (CA) through a certificate signing request. The CA will confirm the signer's identity and provides a signed certificate that ties the signer to the provided public key."}], "metadata": {"source": "Security Considerations for Code Signing", "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 Guide to SSL VPNs:\n\nIntroduction ......................................................................................................................1-1 | | | | 1.1 | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope .................................................................................................1-1 | | | | 1.3 | Audience..................................................................................................................1-1 | | | | 1.4 | Document Structure.................................................................................................1-1 | | | 2."}], "metadata": {"source": "Guide to SSL VPNs", "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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Incident Response?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\nEXECUTIVE SUMMARY .................................................................................................................. IX\nContent of the Report ............................................................................................................................ xi\n CHAPTER 1 DOCUMENT DEVELOPMENT STRATEGY ...................................................................1\n1.1 Cybersecurity and the Electric Sector ............................................................................................ 4\n1.2 Scope and Definitions .................................................................................................................... 5\n1.3 Smart Grid Cybersecurity Document Development Strategy ........................................................ 6\n1.4 Combined Cyber-Physical Attacks .............................................................................................. 12\n CHAPTER 2 LOGICAL ARCHITECTURE AND INTERFACES OF THE SMART GRID ......................14\n2.1 The Seven Domains to the Logical Reference Model ................................................................. 15\n2.2 Logical Security Architecture Overview ..................................................................................... 24\n2.3 Logical Interface Categories ........................................................................................................ 28\n CHAPTER 3 HIGH-LEVEL SECURITY REQUIREMENTS ...............................................................75\n3.1 Cybersecurity Objectives ............................................................................................................. 75\n3.2 Confidentiality, Integrity, and Availability Impact Levels .......................................................... 76\nImpact Levels for the CI&A Categories ......................................................................................"}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "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 A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N provide? (Part 5)"}, {"role": "assistant", "content": "ocument, David Ferraiolo, is a member of the American National Standards Institute/International Committee for Information Technology (ANSI/INCITS) Next Generation Access Control (NGAC) working group.\nTo mitigate the injection of bias, prior drafts have been circulated for review to multiple subject matter experts, as well as formally to the public at large. In addition, prior to publication, the final draft of this document was reviewed by multiple independent entities in compliance with the requirements of the NIST Editorial Review Board (ERB). Disposition and resolution of comments were considered by the authors at large. ## Trademark Information\n\nAll registered trademarks or trademarks belong to their respective organizations. ## Executive Summary\n\nExtensible Access Control Markup Language (XACML) and Next Generation Access Control (NGAC) are very different attribute based access control (ABAC) standards with similar goals and objectives. XACML, available since 2003, is an Extensible Markup Language (XML) based language standard designed to express security policies, as well as the access requests and responses needed for querying the policy system and reaching an authorization decision [1]. NGAC is a relations and architecture-based standard designed to express, manage, and enforce access control policies through configuration of its relations. What are the similarities and differences between these two standards? What are their comparative advantages and disadvantages? These questions are particularly relevant because XACML and NGAC are different approaches to achieving a common access control goal-to allow applications with vastly different access policies to be expressed and enforced using the features of the same underlying mechanism in diverse ways. These are also important questions, given the prevalence of data services in computing."}], "metadata": {"source": "A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Random Number Generation Using Deterministic Random Bit Generators:\n\n| | intended cryptographic strength.' |\n|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Pseudorandom Number Generator | See Deterministic Random Bit Generator . |\n| Random Number | For the purposes of this Recommendation, a value in a set that has an equal probability of being selected from the total population of possibilities and, hence, is unpredictable. A random number is an instance of an unbiased random variable, that is, the output produced by a uniformly distributed random process. |\n| Random Bit Generator (RBG) | A device or algorithm that outputs a sequence of binary bits that appears to be statistically independent and unbiased. An RBG is either a DRBG or an NRBG. |\n| Randomness Source | A component of a DRBG (which consists of a DRBG mechanism and a randomness source) that outputs bitstrings that are used as entropy input by the DRBG mechanism. The randomness source can be an entropy source or an RBG. |\n| Reseed | To acquire additional bits that will affect the internal state of the DRBG mechanism."}], "metadata": {"source": "Recommendation for Random Number Generation Using Deterministic Random Bit Generators", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\naccess control; confidentiality; cryptographic key management system; disaster recovery; federal cryptographic key management system; integrity; metadata; security assessment; security functions; security policies; source authentication. | 9.8 | Ease-of-Use Testing ....................................................................................."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to A Computer Model to Determine Low Cost Techniques to Comply with the Privacy Act of 1974:\n\n1. Data supply obligation notification\n2. Consent for additional use\n3. Check usage authorization\n- A. Usage log maintenance\n5. Record existence notification\n6. Record existence inquiry\n7. Record uses inquiry\n8. Data accuracy\n9. Additional data\n10. Data accuracy inquiry\n11. Subject claim storage\n12. Subject claim dissemination\n13. Retroactive claim dissemination\n14. Record transmission\n15. Consent to transfer data\n16. Legal process notification\n17. Physical security\n18. User training\n19. System assurance\n20. Public notice\n\n```\nU ^' M P A H A ^K'li:? A SS 1 GfJ MFM5 .^'POT NO, OF PFO'TS IN THF MUOhL NKF NO, OF FE'S IN THE MODFL f«iPLC AVG, riO, OF ACCFSS Ct)NTRGL e:NTRlFwS PFP RtCORD t-i{.GS fJO, OF TIMKS PEP YEAR IJSAGP LOG IS SPIAPCHFD FAOY FF-ACTION OF kECOPDS 10 //HJCH \"ADDITIONAL DATA\" tS ADD^n (PFP YEAR) »SCrC vSIZP (^F ilSFP/OPFKATnp TRAJMlKG CLASSPJS FTR A^'^'llA^ THAlN'l'^G VOLUME ^S FRACTION OF INITIAL tPG'-JT ANNUAL PROGRAM r A T N TE N A viC P! FFFUPT AS FRACTION OF I'^'ITIAL DFVt LOpMENT EFFUR r IPIlM PUN COUNTER THE NUMBER OF CPU I ST [JilC T 1 0 G EXECUTED T0-ISC>J SCAN A Flf.E (PER PECOpO) lEpM POPNAT A SI^^PLE REQUEST TO A DATA SUBJECT rCACL CHECK AN ACCESS CONTROL LIST f/.AC WFllE AN ACCtSS CONTPOb Ef'll-Y DATA OT, NF E, lipLC, NLGS/FALY , SCLS,FTR, P^G^nJ^ , I RUN 1 / ? f . , 1 6 , 0 . 5 f 5 2 . U , 0 . 0 0 0 1 , 1 0 , 0 , f ) . 2 , 0 , 2 , U / DATA I sr r.' , T F p H , 7 C AC L , T W AC 1 /2o'jO,, 100(», ,1 000. #500,/ SfATEMEI'l pUNCiroM r)hFlf'lTXON TIMP. TO SORT P RECORDS OF hEUGT'.] r, Si»H(l ,f,) s R « L * O.0OUO21H i 1 r r T fipll T EUPMATS , , 8 00 1 FORMAT ( PGl n ,0) eu0 2 FORI AT f 2G 1 0 ,11, I 1 O, Gl u .0, 2L1 n,G10,0, Ll 0) POOi FnHMAT(4Gl 0,n,LlO|GlO,0,2Ll 0) 8004 EOR-^Ai ( 25' 1 ) 8 0'>S FDPf P r( HfiAl )\n```\n\n- NRLC -The number of record level access control fields per record. - NRPR -The number of record retrieval programs utilizing the data base. - NRUI -Number of record usage inquiries per year."}], "metadata": {"source": "A Computer Model to Determine Low Cost Techniques to Comply with the Privacy Act of 1974", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters provide?"}, {"role": "assistant", "content": "## NISTIR 7711\n\n## Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters\n\n\n\n[This page intentionally left blank. ]\n\n## NISTIR 7711\n\n## Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters\n\nAndrew Regenscheid Geoff Beier\n\nInformation Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nDRAFT\n\nSeptember 2011\n\n\n\nU.S. Department of Commerce Rebecca M. Blank, Acting Secretary\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary for Standards and Technology and Director\n\n[This page intentionally left blank. ]\n\n## Abstract\n\nThis document outlines the basic process for the distribution of election material including registration material and blank ballots to Uniformed and Overseas Citizen Absentee Voting Act (UOCAVA) voters. It describes the technologies that can be used to support the electronic dissemination of election material along with security techniques - both technical and procedural - that can protect this transfer. The purpose of the document is to inform Election Officials about the current technologies and techniques that can be used to improve the delivery of election material for UOCAVA voters. This document is part of a series of documents that address the UOCAVA voting. The first National Institute of Standards and Technology (NIST) publication on UOCAVA voting, entitled NISTIR 7551 A Threat Analysis on UOCAVA Voting Systems , was released in December 2008. In addition to NISTIR 7551, NIST has released NISTIR 7770 Security Considerations for Remote Electronic UOCAVA Voting , Accessibility and Usability Considerations for Remote Electronic UOCAVA Voting, and NISTIR 7682 Information Systems Security Best Practices for UOCAVA-Supporting Systems."}], "metadata": {"source": "Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\n3.1.6 Architectural Locations ... 3.1.6 Architectural Locations\n\nThe selection of cyber resiliency techniques or approaches depends, in part, on where (i. 3.1.6."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Computer Security Division 2015 Annual Report:\n\n| VALIDATION PROGRAMS.............................................................................................................................................................46 | | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| | Cryptographic System Validation.....................................................................................................................................................46 | | | Cryptographic Programs and Laboratory Accreditation...............................................................................................................46 | | | Automated Security Testing and Test Suite Development.............................................................................................................51 | | | Security Content Automation Protocol (SCAP) Validation Program...........................................................................................54 | | | IDENTITY MANAGEMENT | | | ............................................................................................................................................................55 NIST Personal Identity Verification Program (NPIVP)..................................................................................................................."}], "metadata": {"source": "Computer Security Division 2015 Annual Report", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\nThis Handbook is intended primarily for use by Program Office Computer Security Managers (PO-CSM's) at Headquarters and Center Computer Security Managers (CCSM's) at field centers; however, it has been structured to allow anyone from senior management to technical support personnel to quickly understand the overall concepts and their personal relationship to the program. The intention of providing implementation flexibility in the guidance portions is to encourage the exercise of sound judgement by those closest to a problem. PO-CSM's and CCSM's are expected to apply common sense in determining appropriate variations and exceptions that may become necessary in specific computing environments. | Paraaraoh | | | Pace |\n|-------------|-------------------------------------------------------|-------------------------------------------------------|--------|\n| | c. | Personnel Screening | 3-6 |\n| | d. | Access Protection and Accountability | 3-6 |\n| | e. | Compliance Assurance | 3-6 |\n| | f | Contingency and Disaster Recovery Plans | 3-7 |\n| | g- | Approval of Methodologies | 3-7 |\n| 303 | Risk | Assessment Process | 3-7 |\n| 304 | Protective Measures to Prevent Misuse and Abuse | Protective Measures to Prevent Misuse and Abuse | 3-10 |\n| 305 | Certification | Process | 3-10 |\n| | a."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "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 Guide for Security-Focused Configuration Management of Information Systems:\n\nConfiguration Management (CM) comprises a collection of activities focused on establishing and maintaining the integrity of products and systems, through control of the processes for initializing, changing, and monitoring the configurations of those products and systems.\n\n5 Information security is the protection of information and systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability. For the purposes of this publication, 'security' is used synonymously with 'information security,' and 'system' is used synonymously with 'information system.'\n\nThe management of configurations has traditionally been viewed as an IT management best practice. 7 Using SecCM to gain greater control over and ensure the integrity of IT resources facilitates asset management, improves incident response, help desk, disaster recovery and problem solving, aids in software development and release management, enables greater automation of processes, and supports compliance with policies and preparation for audits."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nAs the risk to an information system's confidentiality, integrity and/or availability increases, the need for additional controls to protect the system may also increase accordingly. SP 800-53 Revision 4 provides the security control baselines as the starting point for the security control selection process. The baselines are chosen based on the security category and associated impact level of information systems as described in Federal Information Processing Standard Publication (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems, and FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems .\n\n- Authority and Purpose (AP);\n- Accountability, Audit, and Risk Management (AR);\n- Data Quality and Integrity (DI);\n- Data Minimization and Retention (DM);\n- Individual Participation and Redress (IP);\n- Security (SE);\n- Transparency (TR); and,\n- Use Limitation (UL)."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cell Phone Forensic Tools_ an Overview and Analysis provide? (Part 5)"}, {"role": "assistant", "content": "document is law enforcement, incident response team members, and forensic examiners who are responsible for conducting forensic procedures related to cell phone devices and associated removable media.\n## Table of Contents\n\n| INTRODUCTION......................................................................................................................... | 1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| BACKGROUND........................................................................................................................... | 3 |\n| SUBSCRIBER IDENTITY MODULE.................................................................................................. | 5 |\n| REMOVABLE MEDIA .................................................................................................................... | 6 |\n| FORENSIC TOOLKITS.............................................................................................................."}], "metadata": {"source": "Cell Phone Forensic Tools_ an Overview and Analysis", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Federal S_MIME V3 Client Profile provide? (Part 5)"}, {"role": "assistant", "content": "ipts and vendor B chooses not to, then the signed receipts requested by the user of vendor A's products will never be sent by vendor B's product although neither implementation violates the standards.\nTo help assure that S/MIME products can interoperate and meet the e-mail security needs of federal agencies both with respect to security features, and adequate cryptographic algorithms, NIST has developed this Federal S/MIME V3 Client Profile. This profile states requirements for implementing sets of cryptographic algorithm suites specified elsewhere by the standards development organizations. The profile specifies a set of e-mail security features (e.g., encrypted e-mail, signed receipts) that are mandatory to be implemented. In the definition of this Profile, NIST's intention is never to violate underlying S/MIME standards, but rather to provide additional specificity within the standards. While NIST believes that use of this profile will help assure interoperability of the near term secure e-mail products, NIST anticipates that future revisions of the profile will be required to reflect new cryptographic algorithms and related attacks, new underlying S/MIME standards, and new e-mail security features required by federal agencies. The use of S/MIME requires the establishment of a Public Key Infrastructure (PKI) to support each sender and recipient of S/MIME messages. While the details of PKI are out of scope for this document, it is important to note that PKI is used to provide mechanisms to establish the identity of S/MIME users (known as authentication) and to provide for digital signatures, confidentiality, non-repudiation of sender, etc. X.509 Certificates are used to bind an entity's identity and public key for secure operations for S/MIME and other PKI-enabled secure applications. For a further understanding of PKI, see [Kuhn01], [Housley01], or [Adams00] in the References clause."}], "metadata": {"source": "Federal S_MIME V3 Client Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Cybersecurity of Genomic Data:\n\nFig. 1 summarizes the genomic lifecycle and contrasts those areas that are out of scope for this report-Sample Collection and Sample Preparation-with what is considered in scope-Data Generation and Data Analysis. Additionally, organizations processing genomic data should also consider proper data retention and disposal."}], "metadata": {"source": "Cybersecurity of Genomic Data", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Cryptographic Algorithms and Key Sizes for Personal Identity Verification:\n\nThe cryptographic algorithms, key sizes, and parameters that may be used for these keys are specified in Sec. 3.1. PIV Cards must implement private key computations for one or more of the algorithms identified in this section.\n\nFIPS 201-3 identifies a suite of objects that are stored on the PIV Card for use in authentication mechanisms or other security protocols. These objects may be divided into three classes: cryptographic keys, signed authentication information stored on the PIV Card, and message digests of information stored on the PIV Card. Cryptographic requirements for PIV keys are detailed in Sec. 3.1. Cryptographic requirements for other stored objects are detailed in Sec. 3.2.\n\n## 3.1. PIV Cryptographic Keys"}], "metadata": {"source": "Cryptographic Algorithms and Key Sizes for Personal Identity Verification", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Guide to Bluetooth Security:\n\n3.2.4 Low Energy Secure Connection Key Generation... 3.2.4 Low Energy Secure Connection Key Generation... 3.2.4 Low Energy Secure Connection Key Generation\n\nLow energy Secure Connections security introduced in Bluetooth 4."}], "metadata": {"source": "Guide to Bluetooth Security", "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 Information Integrity?"}, {"role": "assistant", "content": "According to Secure Domain Name System (DNS) Deployment Guide:\n\ndomain name information and maintain the integrity of domain name information in transit. This document provides extensive guidance on maintaining data integrity and performing source authentication.\nAvailability of DNS services and data is also very important; DNS components are often subjected to denial-of-service attacks intended to disrupt access to the resources whose domain names are handled by the attacked DNS components. This document presents guidelines for configuring DNS deployments to prevent many denial-of-service attacks that exploit vulnerabilities in various DNS components."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment Guide", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0 provide? (Part 3)"}, {"role": "assistant", "content": "ith the responsibility to develop or review Protection Profiles. ## Presentation\n\nThis document is presented as a protection profile, followed by a rationale that is structured as a separate document.\nThis format was selected to facilitate using this guidance as a template for the development of Protection Profiles. 1 The Computer Security Act defines the term 'sensitive information' as: any information, the loss, misuse, or unauthorized access to or modification of which could adversely affect the national interest or the conduct of federal programs, or the privacy to which individuals are entitled under section 552a of title 5, United States Code (the Privacy Act), but which has not been specifically authorized under criteria established by an Executive Order or an Act of Congress to be kept secret in the interest of national defense or foreign policy ."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Assessing Security Requirements for Controlled Unclassified Information support CMMC certification?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nother than the ones noted above, are available at\n\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback https://csrc.nist.gov/publications.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283 [1]. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130 [2]. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-04-23 Supersedes NIST Special Publication 800-171A (June 2018) https://doi.org/10.6028/NIST.SP.800-171A\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, Pillitteri V (2024) Assessing Security Requirements for Controlled Unclassified Information and Organizations."}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Recommendation for Random Number Generation Using Deterministic Random Bit Generators:\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. There are two fundamentally different strategies for generating random bits. One strategy is to produce bits non-deterministically, where every bit of output is based on a physical process that is unpredictable; this class of random bit generators (RBGs) is commonly known as non-deterministic random bit generators (NRBGs) 1 . The other strategy is to compute bits deterministically using an algorithm; this class of RBGs is known as Deterministic Random Bit Generators (DRBGs) 2 . | | source of ideal random bitstrings of the same length (see ideal random sequence )."}], "metadata": {"source": "Recommendation for Random Number Generation Using Deterministic Random Bit Generators", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\nTim Grance and Murugiah Souppaya of NIST and Lucinda Gagliano, Thomas Goff, and Pius Uzamere of Booz Allen Hamilton for their keen and insightful assistance throughout the development of the document.\nThe authors would also like to express their thanks to security experts Mike Danseglio (Microsoft), Kurt Dillard (Microsoft), Michael Gerdes (Getronics RedSiren Security Solutions), Peter Szor (Symantec), Miles Tracy (U.S. Federal Reserve System), and Lenny Zeltser (Gemini Systems LLC), as well as representatives from the General Accounting Office, and for their particularly valuable comments and suggestions."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Guidelines for the Secure Deployment of IPv6:\n\n3.1.3 | IPv6 Address Types... 3.1.3 IPv6 Address Types\n\nIPv6 uses the notion of address types for different situations."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "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 AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Guide for Security-Focused Configuration Management of Information Systems:\n\n3.2.3 Non-Component Object CI Baselines\n- 3."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of Information Systems", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Public Safety Mobile Application Security Requirements Workshop Summary:\n\nTo both prepare and adapt to the multitude of circumstances faced by first responders, public safety applications should allow for remote configuration of their power consumption. This configuration can come from two primary sources. The first comes in the form of a power management profile tailored for a first responder's specific needs. For example, a firefighter may have very different power needs from a police officer. Power management profiles for a first responder's specific needs can be applied to a device prior to it entering the field. Applications that expose themselves to this profile could adjust their behavior by changing their network interactions, processing requirements, or shutting themselves off completely.\n\nIt was the consensus of the workshop that app developers should be presented with a baseline set of data protection capabilities/functionality that represents the minimum need for public safety. A baseline set of data protection would need a public safety information classification system or framework. In order to protect data consistently, developers need to know what information can/should be shared, whom can the information be shared with, and how the sharing is controlled. Some information can be shared with anyone. However, protecting the integrity and availability of public information is important. Sensitive information may only be intended for authorized recipients making the confidentiality, integrity, and availability of this data critical. Developers may stand to benefit from unified data dictionaries describing first responder-specific information types and the data protection requirements for each."}], "metadata": {"source": "Public Safety Mobile Application Security Requirements Workshop Summary", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n3.2.2 | Logging Capabilities ... 3.2.2 Logging Capabilities\n\nIDPSs typically perform extensive logging of data related to detected events. 3.2.2 provides more information on ongoing maintenance of the technologies, with Section 3."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”:\n\nAmit Elazari, Intel, described the concept of outcome-based (or performance-based) requirements as a fundamental principle that can be found as a common theme in security policies. She pointed out that the pace of technology innovation means that attack surfaces, the cyber threat landscape, and the overall complexity of the technology ecosystem are constantly evolving, so it is valuable to have requirements that provide flexibility for the future. An example here was that the NIST criteria focus on authentication, whereas other post-Mirai guidance often focused on prohibiting default passwords; the more prescriptive approach could preclude moving on to preferable security solutions. She also saw this approach as useful in building trust with consumers."}], "metadata": {"source": "Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”", "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 Secure Domain Name System (DNS) Deployment Guide provide? (Part 3)"}, {"role": "assistant", "content": "http://csrc.nist.gov/publications. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S.\neconomy 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\nThe Domain Name System (DNS) is a distributed computing system that enables access to Internet resources by user-friendly domain names rather than IP addresses, by translating domain names to IP addresses and back. The DNS infrastructure is made up of computing and communication entities called Name Servers each of which contains information about a small portion of the domain name space. The domain name data provided by DNS is intended to be available to any computer located anywhere in the Internet.This document provides deployment guidelines for securing DNS within an enterprise. Because DNS data is meant to be public, preserving the confidentiality of DNS data. The primary security goals for DNS are data integrity and source authentication, which are needed to ensure the authenticity of domain name information and maintain the integrity of domain name information in transit. This document provides extensive guidance on maintaining data integrity and performing source authentication."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment Guide", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 NIST SP 800-171 control 3.0.1?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case:\n\n3.0.1."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "nist_control": "3.0.1", "cmmc_practice_id": "", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security Recommendations for Server-based Hypervisor Platforms:\n\n- Providing selective connectivity or isolation between groups of VMs belonging to different logical groupings (e.g., different tenants in the case of an Infrastructure as a Service (IaaS) cloud service; different application tiers such as Web Server or Database Server; or different Line of Business applications of an enterprise)\n- Dedicating subnets for key functions such as (a) migration of VMs from one hypervisor host to another for security or performance reasons, (b) attaching network-based storage devices, and (c) fault Tolerant Logging\n- Providing access to the management interface in the management VM (a node of the virtual network), which is used for performing key hypervisor baseline functions of VM lifecycle management (HY-BF4) and Management of hypervisor platform (HY-BF5)"}], "metadata": {"source": "Security Recommendations for Server-based Hypervisor Platforms", "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 Computer Security Division 2013 Annual Report:\n\n| Welcome Letter | ..................................................................1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|\n| Computer Security Division (CSD) Management Team.......2 | |\n| Computer Security Division Organization | ..........................3 |\n| The Computer Security Division Implements the Federal Information Security Management Act | .................7 |\n| Program & Project Achievements for Fiscal Year 2013 | .....9 |\n| NIST Responsibilities Under Executive Order 13636, 'Improving Critical Infrastructure Cybersecurity' | ....................10 |\n| Contributions to National and International Standards Development...........................................................................11 | |\n| Identity Management Standards within INCITS B10 and ISO JTC1/SC 17 ................................................................"}], "metadata": {"source": "Computer Security Division 2013 Annual Report", "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 Configuration Management?"}, {"role": "assistant", "content": "According to A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data:\n\nThe rest of the publication is organized as follows. Section 2 presents an overview of hypervisor taxonomy and briefly describes the architecture of Xen and KVM hypervisor products as well as related work in the area of vulnerability/forensic analysis. Section 3 discusses the gathering of recent vulnerabilities in the two hypervisor products and the classification of those vulnerabilities in terms of hypervisor functionality, attack types and attack sources. Section 4 describes the sample attacks, information gathered in the initial log configuration, and discusses the gaps in forensic evidence that is required for fully detecting and reconstructing those attacks. Identification and discussion of techniques required to gather the needed evidence and the inclusion of those techniques in subsequent attack runs are also part of this section. Section 5 provides the summary and benefits. The NIST-NVD is the U.S. government repository of standards-based vulnerability management data and includes databases of security checklist references, security-related software flaws, misconfigurations, product names, and impact metrics [14]. The first task of the first step is to obtain all vulnerabilities (tagged with Common Vulnerabilities and Exposures (CVE) numbers)) in two open-source hypervisors (Xen and KVM) from the NIST-NVD for the years 2016 and 2017."}], "metadata": {"source": "A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data", "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 Automation Support for Control Assessments_ Project Update and Vision provide? (Part 2)"}, {"role": "assistant", "content": "ter 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).\n## Abstract\n\nIn 2017, the National Institute of Standards and Technology (NIST) published a methodology for supporting the automation of Special Publication (SP) 800-53 control assessments in the form of Interagency Report (IR) 8011. IR 8011 is a multi-volume series that starts with an overview of the methodology (volume 1) and provides guidance and specifications for automating the assessment of controls that support specific information security continuous monitoring security capabilities, one volume per capability. Four volumes have been released so far, and more volumes are in development. In 2023, the NIST Risk Management Framework project responsible for the development and maintenance of Federal Information Security Modernization Act (FISMA)-supporting technical publications and the IR 8011 series performed an internal review of the IR 8011 project. This review yielded results that offered the IR 8011 Development Team opportunities to improve the current IR 8011 methodology, facilitate its adoption, and more. This cybersecurity white paper summarizes some of the findings from this internal review. ## Keywords\n\nactual state; assessment; attack; automation; capability; community of interest; CoI; control; control assessment; control item; defect; defect check; defend; desired state specification; FISMA; information security continuous monitoring; ISCM; methodology; monitoring; ongoing assessment; privacy; risk; risk management; security; security automation. ## Table of Contents\n\n| 1."}], "metadata": {"source": "Automation Support for Control Assessments_ Project Update and Vision", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 A Formal Description of the SDNS Security Protocol at Layer 4 (SP4):\n\n## 3.2.1 SP4E External to Transport\n\n## 3.2.2 Connectionless Network Interface\n\n## 3.2.4 Estelle Idiosyncrasies"}], "metadata": {"source": "A Formal Description of the SDNS Security Protocol at Layer 4 (SP4)", "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 Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”:\n\nfectively monitor and address IoT product security risks. Jasyn briefly summarized the threat landscape and some recent high-profile events as motivating factors for OEMs to consider product security.\nHe then described in detail Zebra's approach, based on three principles:\n\nThere were some discussions on distinctions between IT and IoT, and how some assumptions about how security is implemented in IT products do not hold for IoT products, particularly when addressing safety, privacy, different types of supply chains, and the often unique and highly-diverse and complex environments within which the IoT devices are used. Panelists generally agreed that consideration of complete IoT products, instead of the specific IoT devices, will require changes in the ways in which associated risk assessments are performed, necessarily widening the scope. It will also change the ongoing risk management activities, requiring more types of activities to address the full IoT product instead of just considering the IoT device. This, in turn, will require the ability to obtain more information from throughout the supply chain. For"}], "metadata": {"source": "Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”", "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 Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012 provide? (Part 2)"}, {"role": "assistant", "content": "ion systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems.\nThis guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A-130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other Federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## National Institute of Standards and Technology Interagency Report 7916 276 pages (February 2013)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies:\n\n1. Immersive Technology Ecosystem and Use Cases '[T]he ecosystem of entities that support immersive technologies. This ecosystem encompasses a range of entities and roles that may have complex, multi-directional relationships. Complexity can increase when entities are supported by a chain of sub-entities (e.g., manufacturers supported by multiple component suppliers).'\n2. Immersive Technology Ecosystem and Use Cases '[C]urrent and potential future uses and misuses of immersive technologies across all applicable sectors and user bases, including any barriers to adoption.'\n3. Privacy and Cybersecurity Risk Considerations 'Immersive technologies may generate cybersecurity and privacy risks, some of which can be novel or mix in complex ways.'\n4. Immersive Technology Standards and Risk Management Resources 'Immersive technologies may break existing cybersecurity and privacy assumptions, requiring adaptation or update to tools and techniques documented in standards and guidelines. Additionally, immersive technologies may warrant new standards and guidelines efforts to complement existing resources.'\n\nNIST seeks comment on the ecosystem of entities that support immersive technologies. This ecosystem encompasses a range of entities and roles that may have complex, multi-directional relationships. Complexity can increase when entities are supported by a chain of sub-entities (e.g., manufacturers supported by multiple component suppliers). In particular, NIST seeks stakeholder feedback on the following topics:"}], "metadata": {"source": "Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to PBX Administrator’s Security Standards:\n\nl Operations | 2-3 |\n| Call Diverter Schemes | 2-3 |\n| Remote Access Fraud | 2-3 |\n| Voice Mail Fraud | .\n2-4 |\n| Recent Telephone Industry Trends | 2-5 |\n| Section 3: PBX Administration | |\n| Summary of Responsibilities | 3-1 |\n| Duties and Responsibilities | 3-3 |\n| Know Your PBX | 3-3 |\n| Monitor PBX Options and Settings | 3-3 |\n| Set Passwords | 3-3 |\n| Review Telephone Bills | 3-4 |\n| Educate Fellow Employees | 3-5 |\n| Set Time and Day Restrictions | 3-5 |\n| Destroy Old PBX Manuals | 3-6 |\n| Protect Corporate Telephone Books | 3-6 |\n| Know the Symptoms of PBX Fraud | 3-6 |\n| Know the Symptoms of Voice Mail Fraud | 3-7 |\n| Protect Your Voice Mail System | 3-7 |\n| Restrict DID and Outward Calling Access | 3-8 |\n| Prohibit DISA Use | |\n| Restrict Call Transfer Capabilities | 3-9 3-10 |\n| Change System Administrator Passwords | 3-11 |\n| Limit Country Code Access | 3-12 |"}], "metadata": {"source": "PBX Administrator’s Security Standards", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Security and Privacy Controls for Information Systems and Organizations provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-53\nRevision 5\n\nSecurity and Privacy Controls for\nInformation Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53r5\n\n\fNIST Special Publication 800-53\nRevision 5\n\n Security and Privacy Controls for\n\nInformation Systems and Organizations\n\nJOINT TASK FORCE\n\nThis publication is available free of charge from:\nhttps://doi.org/10.6028/NIST.SP.800-53r5\n\nSeptember 2020\nINCLUDES UPDATES AS OF 12-10-2020; SEE PAGE XVII\n\nNational Institute of Standards and Technology\n Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nU.S. Department of Commerce\nWilbur L. Ross, Jr., Secretary\n\n\fT\nh\ns\n\ni\n\np\nu\nb\n\nl\ni\n\nc\na\n\nt\ni\n\no\nn\n\ni\n\ns\n\na\nv\na\n\ni\nl\n\nl\n\na\nb\ne\nf\nr\ne\ne\no\nf\n\nc\nh\na\nr\ng\ne\nf\nr\no\nm\n\n:\n\nh\nt\nt\np\ns\n:\n/\n/\nd\no\ni\n. o\nr\ng\n/\n1\n0\n. 6\n0\n2\n8\n/\nN\nS\nT\nS\nP\n. 8\n0\n0\n-\n5\n3\nr\n5\n\n. I\n\nNIST SP 800-53, REV. 5 SECURITY AND PRIVACY CONTROLS FOR INFORMATION SYSTEMS AND ORGANIZATIONS\n_________________________________________________________________________________________________\n\nAuthority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the\nFederal Information Security Modernization Act (FISMA), 44 U.S.C. § 3551 et seq., Public Law\n(P.L.) 113-283. NIST is responsible for developing information security standards and guidelines,\nincluding minimum requirements for federal information systems. Such information security\nstandards and guidelines shall not apply to national security systems without the express\napproval of the appropriate federal officials exercising policy authority over such systems. This\nguideline is consistent with the requirements of the Office of Management and Budget (OMB)\nCircular A-130."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile:\n\n| CSF Element | CSF Element Description | Priority | Recommendations, Considerations, Notes assist with maintaining cross-references | |---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ID.RA-09 | The authenticity and integrity of hardware and software are assessed prior to acquisition and use | Medium | N1: See the notes for ID.RA."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Recommendation for Random Bit Generator (RBG) Constructions:\n\n3.1.3 status = DRBG\\_Reseed ( RBG3\\_DRBG\\_state\\_handle, extra\\_bits || additional\\_input ) . 3.1.3, the Get\\_randomness\\_source\\_input call in the DRBG\\_Reseed function is replaced by:\n\n- o ( status , seed\\_material ) = Get\\_entropy\\_bitstring ( s , Method\\_1 ) ."}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "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 AT.L2-3.2.8 (NIST 3.2.8)?"}, {"role": "assistant", "content": "According to Guidelines for Securing Radio Frequency Identification (RFID) Systems:\n\n3.2.8. 3.2.8 Tag Polling\n\nControl: A reader periodically queries the tag to determine its continued presence and operating status. 3.2.8 Tag Polling | X | | | | |\n| 5."}], "metadata": {"source": "Guidelines for Securing Radio Frequency Identification (RFID) Systems", "cmmc_level": "all", "nist_control": "3.2.8", "cmmc_practice_id": "AT.L2-3.2.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies:\n\n3.5.1 Privacy And Information Security Provisions\n\nSection 5, 'Policy,' subparagraph f, 'Privacy and Information Security,' subparagraph 2), 'Information Security,' requires agencies to provide proper safeguards to:\n\n- a) Ensure that the CIO designates a senior agency information security officer to develop and maintain an agency-wide information security program in accordance with the Federal Information Security Modernization Act of 2014;\n- b) Protect information in a manner commensurate with the risk that would result from unauthorized access, use, disclosure, disruption, modification, or destruction of such information; and\n- c) Implement security policies issued by OMB, as well as requirements issued by the Department of Commerce, the Department of Homeland Security (DHS), the General Services Administration (GSA), and the Office of Personnel Management (OPM)."}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to An Industrial Control System Cybersecurity Performance Testbed:\n\nReceptacle for Machining Stations .....................................................................................12 | | 3.2.3.1 | Robot Assembly Table.....................................................................................................12 | Robot Assembly Table.....................................................................................................12 | | 3.2.4 | Emergency Stop Operation.................................................................................................13 | Emergency Stop Operation.................................................................................................13 | | 3.2.5 | Software Architecture.........................................................................................................14 | Software Architecture.........................................................................................................14 | | 3.2.5.1 | Control Layer...................................................................................................................14 | Control Layer...................................................................................................................14 | | 3.2.5.2 | PLC I/O Layer...................................................................................................................15 | PLC I/O Layer...................................................................................................................15 | | 3.2.5.3 | ROS Bags .........................................................................................................................15 | ROS Bags .........................................................................................................................15 | | 3.2.5.4 | ROS versus ROS Industrial...............................................................................................15 | ROS versus ROS Industrial...............................................................................................15 | | 3.2.5.5 | Theory of Operation........................................................................................................15 | Theory of Operation........................................................................................................15 | | 3.2.6 | Final Assembly.....................................................................................................................16 | Final Assembly.....................................................................................................................16 | | 3.3 | Third Enclave Concepts...............................................................................................................16 | Third Enclave Concepts...............................................................................................................16 | | 3.3.1 | Intelligent Transportation System ......................................................................................16 | Intelligent Transportation System ......................................................................................16 | | 3.3.2 | Wide-area Networks with SCADA.......................................................................................16 | Wide-area Networks with SCADA.......................................................................................16 |"}], "metadata": {"source": "An Industrial Control System Cybersecurity Performance Testbed", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to Guidelines on Securing Public Web Servers:\n\n3.2.4 | Web Server and Network Administrators ... 3.2.4 Web Server and Network Administrators\n\nWeb server administrators are system architects responsible for the overall design, implementation, and maintenance of a Web server."}], "metadata": {"source": "Guidelines on Securing Public Web Servers", "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 Information Integrity?"}, {"role": "assistant", "content": "According to Understanding Stablecoin Technology and Related Security Considerations:\n\nThe growth of the stablecoin market and its associated identified risks have centered much research on stablecoins, usually with a focus on economic aspects. For example, the U.S. Treasury evaluates stablecoin risks in [5]. These risks include concerns about investor protection and market integrity, encompassing 'possible fraud and misconduct in digital asset trading, including market manipulation, insider trading, and front running, as well as a lack of trading or price transparency'. As stablecoins are increasingly used for complex financial arrangements and massive leveraging, the U.S. Treasury envisions possible risks to the broader financial system. In addition, it explores how stablecoin use could challenge efforts to govern 'anti-money laundering (AML), countering the financing of terrorism (CFT), and proliferation'. Lastly, it explores prudential risks for stablecoins, where stablecoin issuers may not maintain sufficient reserves or an effective method to support redemptions in times of stress. A complementary evaluation of the economic aspects of stablecoins is [1], which explores the possible impacts of stablecoins on the banking system and credit intermediation. IOSCO [4] presents another risk analysis (with a regulatory focus) and enumerates stablecoin risks related to 'consumer protection, market integrity, transparency, conflicts of interest, financial crime, systemic implications and economic impacts'. A deep analysis of how fiat-based stablecoins maintain their stability is found in [6], which evaluates how the price stabilization of stablecoins differs from national currencies pegged to one another. Finally, the specific risks of uncollateralized algorithmic stablecoins are highlighted in [2]."}], "metadata": {"source": "Understanding Stablecoin Technology and Related Security Considerations", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\ns://doi.org/10.6028/NIST.SP.800-160v1r1\n- [17] Boyens JM, Smith AM, Bartol N, Winkler K, Holbrook A, Fallon M (2022) Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-161r1-upd1, Includes updates as of November 1, 2024. https://doi.org/10.6028/NIST.SP.800-161r1-upd1\n- [18] Heckert N, Filliben J, Croarkin C, Hembree B, Guthrie W, Tobias P, Prinz J (2012) NIST/SEMATECH e-Handbook of Statistical Methods. (National Institute of Standards and Technology, Gaithersburg, MD). https://doi.org/10.18434/M32189\n- [19] Stevens SS (1946) On the Scales of Measurement. Science 103(2684):677-680. http://www.jstor.org/stable/1671815\n- [20] Turan MS, Barker E, Kelsey J, McKay KA, Baish ML, Boyle M (2018) Recommendation for the Entropy Sources Used for Random Bit Generation. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-90B. https://doi.org/10.6028/NIST.SP.800-90B\n- [21] Stolfo S, Bellovin S, Evans D (2011) Measuring Security. IEEE Security & Privacy 9(3):6065. https://doi.org/10.1109/MSP.2011.56\n- [22] Ross R, Pillitteri V, Graubart R, Bodeau D, McQuaid R (2021) Developing Cyber-Resilient Systems: A Systems Security Engineering Approach. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-160v2r1. https://doi.org/10.6028/NIST.SP.800-160v2r1\n- [23] Schroeder K, Trinh H, Pillitteri VY (2024) Measurement Guide for Information Security: Volume 2 - Developing an Information Security Measurement Program. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-55v2. https://doi.org/10.6028/NIST.SP.800-55v2"}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security Considerations for Voice Over IP Systems:\n\nt a central point ensures all VOIP traffic emanating from the enterprise network has been encrypted. Newer IP phones are able to provide Advanced Encryption System (AES) encryption at reasonable cost.\nNote that Federal Information Processing Standard (FIPS) 140-2, Security Requirements for Cryptographic Modules, is applicable to all Federal agencies that use cryptographic-based security systems to protect sensitive information in computer and telecommunication systems (including voice systems) as defined in Section 5131 of the Information Technology Management Reform Act of 1996, Public Law 104-106. 2. Ensure that the organization has examined and can acceptably manage and mitigate the risks to their information, system operations, and continuity of essential operations when deploying VOIP systems."}], "metadata": {"source": "Security Considerations for Voice Over IP Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice MA.L2-3.7.1 (NIST 3.7.1)?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\n3.7.1. 3.7.1. 3.7.1."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "nist_control": "3.7.1", "cmmc_practice_id": "MA.L2-3.7.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Best Practices for Privileged User PIV Authentication:\n\nFor many years, most organizations, including federal agencies, have relied heavily on password-based single-factor user authentication. There are many types of threats against this form of authentication, including the following:\n\nAll of these threats can be exploited by an attacker obtaining the identity credential (the singlefactor password) of a legitimate user to gain unauthorized access to an agency's systems and/or networks with that user's privileges. If a password is used across multiple systems, the compromise of this password enables unauthorized access to all the other systems. There are some controls available to counter these threats, but they have limited effectiveness, so the threats as a whole against password-based single-factor user authentication can only be slightly mitigated. Many attackers leverage the impersonation of a regular user into greater access to an agency's systems and networks by issuing subsequent attacks to escalate privileges and gain administrative-level access. This, in turn, can be used to move from system to system, surreptitiously traveling through the enterprise to eventually reach a High Value Asset. 3 Administrative-level access can also be used to tamper with system integrity by establishing backdoors into the system, such as creating additional privileged accounts or altering a service to permit unauthorized access to the system. An attacker can use these backdoors to gain persistent access to the system.\n\nFor more information on general threat models and mitigations for the identity management lifecycle, including identity proofing, registration, issuance, and revocation, see the latest revision of NIST SP 800-63 [2] ."}], "metadata": {"source": "Best Practices for Privileged User PIV Authentication", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guidelines on Active Content and Mobile Code:\n\nBesides spyware, Web site developers have a myriad of tools at their disposal to collect personal information. They include tracking site use by storing persistent information known as cookies via a user's browser; embedding invisible single-pixel images within HTML called Web bugs that serve as a signal of page access; and invoking the communication capabilities of downloaded scripts and program components."}], "metadata": {"source": "Guidelines on Active Content and Mobile Code", "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 Automation Support for Security Control Assessments_ Software Vulnerability Management provide? (Part 5)"}, {"role": "assistant", "content": "this document. ## Document Conventions\n\nThe terms 'shall' and 'shall not' indicate requirements to be followed strictly in order to conform to the publication and from which no deviation is permitted.\nThe terms 'should' and 'should not' indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. The terms 'may' and 'need not' indicate a course of action permissible within the limits of the publication. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical or causal. The security capability designation 'VULN' was utilized in previous volumes of NISTIR 8011 in reference to the Software Vulnerability Management security capability. For greater consistency with industry, academia, and other federal agencies, the more widely used designation for the Software Vulnerability Management security capability, 'VUL,' replaces VULN herein and in future NISTIR 8011 volumes when referring to the Software Vulnerability Management security capability. ## 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."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Vulnerability Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Technical Guide to Information Security Testing and Assessment:\n\nFor internal security testing, assessors work from the internal network and assume the identity of a trusted insider or an attacker who has penetrated the perimeter defenses. This kind of testing can reveal vulnerabilities that could be exploited, and demonstrates the potential damage this type of attacker could cause. Internal security testing also focuses on system-level security and configuration-including application and service configuration, authentication, access control, and system hardening. Log review determines if security controls are logging the proper information, and if the organization is adhering to its log management policies. 7 As a source of historical information, audit logs can be used to help validate that the system is operating in accordance with established policies. For example, if the logging policy states that all authentication attempts to critical servers must be logged, the log review will determine if this information is being collected and shows the appropriate level of detail. Log review may also reveal problems such as misconfigured services and security controls, unauthorized accesses, and attempted intrusions. For example, if an intrusion detection system (IDS) sensor is placed behind a firewall, its logs can be used to examine communications that the firewall allows into the network. If the sensor registers activities that should be blocked, it indicates that the firewall is not configured securely. - GLYPH<c=31,font=/DGCOEC+Webdings> Authentication server or system logs may include successful and failed authentication attempts. - GLYPH<c=31,font=/DGCOEC+Webdings> System logs may include system and service startup and shutdown information, installation of unauthorized software, file accesses, security policy changes, account changes (e.g., account creation and deletion, account privilege assignment), and privilege use."}], "metadata": {"source": "Technical Guide to Information Security Testing and Assessment", "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 Communications Protection?"}, {"role": "assistant", "content": "According to A Security Perspective on the Web3 Paradigm:\n\nBetween the late 1980s and early 2000s, the internet hosted very basic websites that were mostly comprised of text (often just plain text but sometimes with simple formatting), images, and hyperlinks to other webpages. As a result, this era has since been dubbed the 'static' or 'read-only' web. Most websites were hosted by large organizations, government agencies, internet service providers, or tech-savvy users who were allotted a small portion of web storage from their internet service provider or other web-hosting provider to develop their own 'home page.' Websites eventually began to create more designs and styles via Hypertext Markup Language (HTML) tables, which allowed developers to change the format of their page. During this period, there were also some 'dynamic' pages on the web that used the Common Gateway Interface (CGI) to execute code on the server and generate a static webpage to be delivered to the end user. There were little to no client-side manipulatable websites. Online communications were done through email, bulletin boards, and forums, and there was almost no online shopping. Since there was not a lot of user interaction, organizations did not host massive amounts of user data. Web3 utilizes existing internet technologies that make up much of the current web architecture, such as Transmission Control Protocol/Internet Protocol (TCP/IP), remote procedure call (RPC), and Transport Layer Security (TLS). It can also use existing web services, servers, databases, and webpages to act as an interface. Web3 applications can be designed to interact with (as both input to and utilize output from) existing systems. Like blockchain systems and cryptocurrency systems, Web3 leverages well-known technologies, such as publickey cryptography, digital signatures, and cryptographic hashing algorithms. - [20] Department of Financial Protection & Innovation (2023) Crypto Scam Tracker."}], "metadata": {"source": "A Security Perspective on the Web3 Paradigm", "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 Glossary of Computer Security Terminology provide? (Part 3)"}, {"role": "assistant", "content": "sitiue to aborted connections, and do not detect the disconnect and reset for the next user. Continued aborts are considered [improper], and may result in a warning or revocation of access privileges.\n(BBD) |\n|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| acceptable level of risk | A judicious and carefully considered assessment by the appropriate designated approving authority (DAA) that an automatic data processing (ADP) activity or network meets the minimum requirements of applicable security directives. The assessment should take into account the value of ADP assets; threats and vulnerabilities; countermeasures and their efficacy in compensating for vulnerabilities; and operational requirements. (OPNAVINST 5239.1 A) |\n| acceptance | Indicates a facility or system generally meets technical and performance standards but may have minor exceptions which do not keep the facility from meeting operational and security requirements, (APR 700-10) |\n| acceptance inspection | The final inspection to determine if a facility or system meets the specified technical and performance standards. It is held immediately after facility and software testing and is the basis for commissioning or accepting the information system."}], "metadata": {"source": "Glossary of Computer Security Terminology", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 MP.L2-3.8.1 (NIST 3.8.1)?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n3.8.1, 3."}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "nist_control": "3.8.1", "cmmc_practice_id": "MP.L2-3.8.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Cell Phone Forensic Tools_ an Overview and Analysis Update:\n\nThe acquisition process begins by successfully logging into the PhoneBase2 application via either Admin or an assigned username, creating a case (e.g., File -> New) and adding a unique record to a database provided with the PhoneBase2 software, as illustrated below in Figure 34 and Figure 35."}], "metadata": {"source": "Cell Phone Forensic Tools_ an Overview and Analysis Update", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0:\n\n| TRUSTED PATH/CHANNELS (FTP)...........................................................................................\n| B22 |\n| B.10.1 | FTP_ITC.1-CSPP Inter-TSF trusted channel | ................................................................ B22 |\n| C. APPENDIX C: TOE ASSURANCE REQUIREMENT DETAILS...........................................C1 | C. APPENDIX C: TOE ASSURANCE REQUIREMENT DETAILS...........................................C1 | |\n| C.1 | CONFIGURATION MANAGEMENT (ACM)................................................................................. | C1 |\n| C.1.1 | ACM_CAP.3 Authorization controls..................................................................................."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to User's Guide to Telework and Bring Your Own Device (BYOD) Security:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "User's Guide to Telework and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Forensics Web Services (FWS) provide? (Part 5)"}, {"role": "assistant", "content": "|\n| | 2.3 | Static vs.\nDynamic Composition .................................................................................3 |\n| | 2.4 | Hierarchical vs, Conversational Composition……………………………………………4 |\n| | 2.5 | Composition Standards and Languages.....................................................................4 |\n| | 2.6 | Web ServicesExample…………………………………………………………………….5 |\n| 3. | WEBSERVICEATTACKS………………………………………………………………………..6 | WEBSERVICEATTACKS………………………………………………………………………..6 |\n| 4. | CHALLENGES IN FORENSICS OF WEB SERVICES………………………………………...8 | CHALLENGES IN FORENSICS OF WEB SERVICES………………………………………...8 |\n| 5."}], "metadata": {"source": "Forensics Web Services (FWS)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nBalancing exposure to cybersecurity risks throughout the supply chain with the costs and benefits of implementing C-SCRM practices and controls should be a key component of the acquirer's overall approach to C-SCRM. Enterprises should be aware that implementing C-SCRM practices and controls necessitates additional financial and human resources. Requiring a greater level of testing, documentation, or security features from suppliers, developers, system integrators, external system service providers, and other ICT/OT-related service providers may increase the price of a product or service, which may result in increased cost to the acquirer. This is especially true for those products and services developed for general-purpose applications and not tailored to the specific enterprise security or C-SCRM requirements. When deciding whether to require and implement C-SCRM practices and controls, acquirers should consider both the costs of implementing these controls and the risks of not implementing them."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\n3.3.2 Building Blocks for CI/CD Pipelines | ... 3.3.2 Building Blocks for CI/CD Pipelines\n\nThe primary software for defining CI/CD pipeline resources, building the pipelines, and executing those pipelines is the CI/CD pipeline software."}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "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 is CMMC practice AU.L2-3.3.6 (NIST 3.3.6)?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\n3.3.6 | Storage Network (Tap Into, Alter to Gain Access)... 3.3.6 Storage Network (Tap Into, Alter to Gain Access)\n\nWhen storage clients consume data from the storage systems, the data is transferred through a variety of storage network components (i."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "nist_control": "3.3.6", "cmmc_practice_id": "AU.L2-3.3.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 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 System and Communications Protection?"}, {"role": "assistant", "content": "According to Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities:\n\n- GLYPH<c=31,font=/KKMIHL+Webdings> Training. For the purposes of this publication, training refers only to informing personnel of their roles and responsibilities within a particular IT plan and teaching them skills related to those roles and responsibilities, thereby preparing them for participation in exercises, tests, and actual emergency situations related to the IT plan. Training personnel on their roles and responsibilities before an exercise or test event is typically split between a presentation on their roles and responsibilities, and activities that allow personnel to demonstrate their understanding of the subject matter. - GLYPH<c=31,font=/KKMIHL+Webdings> Exercises. An exercise is a simulation of an emergency designed to validate the viability of one or more aspects of an IT plan. In an exercise, personnel with roles and responsibilities in a particular IT plan meet to validate the content of a plan through discussion of their roles and their responses to emergency situations, execution of responses in a simulated operational environment, or other means of validating responses that does not involve using the actual operational environment. Exercises are scenario-driven, such as a power failure in one of the organization's data centers or a fire causing certain systems to be damaged, with additional situations often being presented during the course of an exercise. There are several types of exercises, and this publication focuses on the following two types that are widely used in TT&E programs by single organizations:\n- -Tabletop Exercises. Tabletop exercises are discussion-based exercises where personnel meet in a classroom setting or in breakout groups to discuss their roles during an emergency and their responses to a particular emergency situation."}], "metadata": {"source": "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\n3.2.1 Common Notions of Protection 3-3 3. 3.2.1 Common Notions of Protection\n\n\"Conventional wisdom\" holds that the military is concerned only with protecting the confidentiality of classified information."}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Zero Trust Architecture:\n\n| ACT-IAC | American Council for Technology and Industry Advisory Council. (2019). Zero Trust Cybersecurity Current Trends . Disponible en https://www.actiac.org/zero- trust-cybersecurity-current-trends |\n|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Anderson | Anderson B., McGrew D. (2017). Machine Learning for Encrypted Malware Traffic Classification: Accounting for Noisy Labels and Non- Stationarity. Proceedings of the 23rd ACMSIGKDD International Conference on Knowledge Discovery and Data Mining (ACM, Halifax, Nova Scotia, Canada), pp. 1723-1732. https://doi.org/10.1145/3097983.3098163 |\n| BCORE | Department of Defense CIO. (2007). Department of Defense Global Information Grid Architecture Vision Version 1.0 June 2007. Disponible en http://www.acqnotes.com/Attachments/DoD%20GIG%20Architectural% 20Vision,%20June%2007.pdf |\n| CSA-SDP | Cloud Security Alliance. (2015). SDP Specification 1.0. Disponible en https://cloudsecurityalliance.org/artifacts/sdp-specification-v1-0/ |\n| FIPS199 | National Institute of Standards and Technology. (2004). Standards for Security Categorization of Federal Information and Information Systems. (U."}], "metadata": {"source": "Zero Trust Architecture", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.1.1. 3.1.1) • Deprecated the CHUID data object's Authentication Key Map data element • Deprecated the Printed Information data object's Employee Affiliation Line 2 data element (tag 0x03) • Removed size limits on signed data object containers (Part 1, Appendix A) |\n\n| Version | Release Date | Updates |\n|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| SP 800-73-3 | February 2010 | • Added preamble: I - Revision History, II - Configuration Management, and III - NPIVP Conformance Testing (Part 1, Preamble) • Removed the CHUID data object's Authentication Key Map data element • Removed the Printed Information data object's Employee Affiliation Line 2 data element (tag 0x03) • Deprecated IPv6 as optional value for the CHUID's GUID data element (Part 1, Sec."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Symposium on Federally Funded Research on Cybersecurity of Electric Vehicle Supply Equipment (EVSE) 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\n\nEmail: nistir8294-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\nElectric vehicles are becoming common on the Nation's roads, and the electric vehicle supply equipment infrastructure (EVSE) is being created to support that growth. The NIST Information Technology Lab (ITL) hosted a one-day symposium to showcase federally funded research into the potential cybersecurity implications of EVSE."}], "metadata": {"source": "Symposium on Federally Funded Research on Cybersecurity of Electric Vehicle Supply Equipment (EVSE)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio:\n\n3.1.2. 3.1.2."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "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 Audit and Accountability?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography:\n\n| Incorporating Key Confirmation into a C(0e, 2s) Scheme ..............................\n107 6.3.3.1 C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party |\n| | 6.3.3.2 | C(0e, 2s) Scheme with Unilateral Key Confirmation Provided by Party V to Party U...................................................................................... 109 |\n| | 6.3.3.3 | C(0e, 2s) Scheme with Bilateral Key Confirmation ......................... 110 |\n| 7. Rationale for Selecting a Specific Scheme........................................................ 112 | 7. Rationale for Selecting a Specific Scheme........................................................ 112 | 7. Rationale for Selecting a Specific Scheme........................................................"}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\nIT may include information from EV/XFC partners, utility/building management partners, and suppliers/vendors. Utility/building management owners/operators may consider encrypting all operational data.\n| ISA/IEC 62443-2- 1:D4E1 NET 1.01, NET 1.06, NET 1.08, DATA 1.2, DATA 1.6, USER 1.16 ISA/IEC 62443-3- 3:2013 SR 3.1, SR 3.8, SR 4.1, SR 4.2 |\n| DS-3: Assets are formally managed throughout removal, transfer, and disposition. | Ecosystem: Manage assets, which may include hardware, software, information databases, and developmental/operational tools or systems and the data itself. In addition to the day-to-day management activities, formal asset management includes creating, using, and updating asset management activities or strategies. | [NIST-SP800-53r5] CM-8, MP-6, PE-16, PE-20 NERC CIP 011-2-R2 |\n| DS-3 | EV | Managed data may include information on vehicle performance, battery performance, charging history, location history, and vehicle owners from EV/XFC partners, and suppliers/vendors. Transfer of EV assets should consider including encryption and authentication protocols and should consider only being managed by authorized parties. Consider going through a formal provision process when updating firmware and verifying that updates can only be made by a certified party. Consider including guidelines for data retention, backup, and secure disposal in any procedures. | [NIST-SP800-53r5] CM-8, MP-6, PE-16, PE-20 ISO 24089:2023 5.3.4.1, 7.3.1.3, 7.3.4.7, 9.3.2.7 |\n| DS-3 | XFC/EVSE | Associated data may include information from EV owners, EV/XFC partners, and suppliers/vendors."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice CM.L2-3.4.6 (NIST 3.4.6)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\n3.4.6, 6."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "cmmc_level": "all", "nist_control": "3.4.6", "cmmc_practice_id": "CM.L2-3.4.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n.......................................................................75 |\n| 5.4.1.\nBusiness Associate Contracts or Other Arrangements (§ 164.314(a)).......................................77 |\n| 5.4.2. Requirements for Group Health Plans (§ 164.314(b))................................................................79 |\n| 5.5.1. Policies and Procedures (§ 164.316(a))......................................................................................81 |\n| 5.5.2. Documentation (§ 164.316(b))...................................................................................................83 |\n| References.......................................................................................................................................85 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................87 |\n| Appendix B. Glossary .......................................................................................................................91 |\n| Appendix C."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automation Support for Security Control Assessments_ Software Asset Management 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 information security 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: sec-cert@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 systems. ## Abstract\n\nThe NISTIR 8011 volumes each focus on an individual information security capability, adding tangible detail to the more general overview given in NISTIR 8011 Volume 1, and providing a template for transition to a detailed, NIST guidance-based automated assessment."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Asset Management", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne:\n\nCMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B\n\nCMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B\n\nHawes D, Calis A, Crombie R (2023) Cryptographic Module Validation Program (CMVP) Security Policy Requirements: CMVP Validation Authority Updates to ISO/IEC 24759 and ISO/IEC 19790 Annex B. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-140Br1. https://doi.org/10.6028/NIST.SP.800-140Br1"}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP) Security Policy Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759 and ISO_IEC 19790 Anne", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.1 (NIST 3.5.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n3.5.1. 3.5.1."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security Guidance for First Responder Mobile and Wearable Devices 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. Submit comments on this publication to: NISTIR8235\\_Comments@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. ## Abstract\n\nPublic safety officials utilizing public safety broadband networks will have access to devices, such as mobile devices, tablets and wearables. These devices offer new ways for first responders to complete their missions but may also introduce new security vulnerabilities to their work environment."}], "metadata": {"source": "Security Guidance for First Responder Mobile and Wearable Devices", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities:\n\nSecure Coding Principles | . . . . . . . . . . . . | 47 |\n| | 9.1. | Input/Output Check Safety . . . . . . . . . . . . . . . | 47 |\n| | 9.2. | Memory Safety . . . . . . . . . .\n| 48 |\n| | 9.3. | Data Type Safety . . . . . . . . . . . . . . . . . . | 50 |\n| 10. | BF Tools . . . . . . | . . . . . . . . . . . . . . . | 52 |\n| | 10.1. BFCWE Tool 10.2. | . . . . . . . . . . . . . . . . . . | 52 |\n| | BFCVE Tool | . . . . . . . . . . . . . . . . . . | 53 |"}], "metadata": {"source": "Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to U.S. Department of Energy Risk Assessment Methodology:\n\n## U.S. DEPARTMENT OF ENERGY RISK ASSESSMENT METHODOLOGY\n\nVolume I: DOE Risk Assessment Guideline Instructions, Resource Tabie, and Compieted Sampie\n\nVoiume II: DOE Risk Assessment Woiksheets"}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to CMVP Approved Authentication Mechanisms_ CMVP Validation Authority Requirements for ISO_IEC 19790 Annex E and ISO_IEC 24579 Section 6.17:\n\nauthentication; Cryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140; ISO/IEC 19790; ISO/IEC 24759; testing requirement; vendor evidence; vendor documentation.\n\nThis document is focused toward the vendors, testing labs, and CMVP for the purpose of addressing authentication issues in cryptographic module design, manufacture, and testing.\n\nThis document specifies the Cryptographic Module Validation Program (CMVP) modifications of the methods to be used by a Cryptographic and Security Testing Laboratory (CSTL) to demonstrate conformance. This document also specifies the modification of methods for evidence that a vendor or testing laboratory provides to demonstrate conformity. The approved sensitive security parameter generation and establishment methods specified in this document supersede those specified in ISO/IEC 19790 Annex E and ISO/IEC 24759 paragraph 6.17."}], "metadata": {"source": "CMVP Approved Authentication Mechanisms_ CMVP Validation Authority Requirements for ISO_IEC 19790 Annex E and ISO_IEC 24579 Section 6.17", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines on Security and Privacy in Public Cloud Computing:\n\nThe organization should collect and analyze available data about the state of the system regularly and as often as needed to manage security and privacy risks, as appropriate for each level of the organization (i.e., governance level, mission or business process level, and information systems level) [Dem10]. Continuous monitoring of information security requires maintaining ongoing awareness of privacy and security controls, vulnerabilities, and threats to support risk management decisions. The goal is to conduct ongoing monitoring of the security of an organization's networks, information, and systems, and to respond by accepting, avoiding, or mitigating risk as situations change. -  Staff Specialization. Cloud providers, just as other organizations with large-scale computing facilities, have an opportunity for staff to specialize in security, privacy, and other areas of high interest and concern to the organization. Increases in the scale of computing induce specialization, which in turn allows security staff to shed other duties and concentrate exclusively on security and privacy issues. Through increased specialization, there is an opportunity for staff members to gain in-depth experience and training, take remedial actions, and make improvements to security and privacy more readily than otherwise would be possible with a more diverse set of duties. -  Platform Strength. The structure of cloud computing platforms is typically more uniform than that of most traditional computing centers. Greater uniformity and homogeneity facilitate platform hardening and enable better automation of security management activities like configuration control, vulnerability testing, security audits, and security patching of platform components."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "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 Guidelines for API Protection for Cloud-Native Systems:\n\n...............14 |\n| 2.7.5. Reaching Out to Other Systems .................................................................................................15 |\n| 2.7.7.\nIdentity Canonicalization............................................................................................................16 |\n| 3. Recommended Controls for APIs...................................................................................................17 |\n| 3.1.1. Basic Pre-Runtime Protections...................................................................................................18 |\n| 3.1.2. Advanced Pre-Runtime Protections ...........................................................................................19 |\n| 3.2.1. Basic Runtime Protections..........................................................................................................20 |"}], "metadata": {"source": "Guidelines for API Protection for Cloud-Native Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nand security for wireless implantable medical devices,' Proceedings of the 28th international conference on Human factors in computing systems, ACM New York, NY, USA, 2010, pp 917-926.\n- [7] National Institute of Standards and Technology 'FIPS Pub 199: Standards for Security Categorization of Federal Information and Information Systems,' FEDERAL INFORMATION PROCESSING STANDARDS PUBLICATION, February 2004. - [8] S. Fischer and M. Zitterbart, 'Security in Sensor Networks,' Information Technology: Vol. 52, No. 6, 2010, pp. 311-312."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Measuring the Usability and Security of Permuted Passwords on Mobile Platforms provide?"}, {"role": "assistant", "content": "## NISTIR 8040\n\n## Measuring the Usability and Security of Permuted Passwords on Mobile Platforms\n\nKristen K. Greene John Kelsey\n\nJoshua M. Franklin\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8040\n\n\n\n## NISTIR 8040\n\n## Measuring the Usability and Security of Permuted Passwords on Mobile Platforms\n\nKristen K. Greene Information Access Division Information Technology Laboratory\n\nJohn Kelsey Computer Security Division Information Technology Laboratory\n\nJoshua M. Franklin Applied Cybersecurity Division Information Technology Laboratory\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8040\n\nApril 2016\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology\n\n## National Institute of Standards and Technology Internal Report 8040 65 pages (April 2016)\n\n## This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.IR.8040\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": "Measuring the Usability and Security of Permuted Passwords on Mobile Platforms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 General Access Control Guidance for Cloud Systems provide? (Part 3)"}, {"role": "assistant", "content": "h to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sp800-210-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 document presents cloud access control characteristics and a set of general access control guidance for cloud service models: IaaS (Infrastructure as a Service), PaaS (Platform as a Service), and SaaS (Software as a Service)."}], "metadata": {"source": "General Access Control Guidance for Cloud Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\napplications. Since microservices are typically implemented as containers, a container orchestration and resource management platform are used for deployment, operations, and maintenance of services.\nThe purpose of creating the CI/CD pipeline is to enable frequent updates to source code, rebuilds, and the automatic deployment of updated modules into the production environment. The key tasks involved are [19]:"}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "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 Guidelines for the Secure Deployment of IPv6:\n\n..................................................................... | Introduction ...................................................................................................................\n| 1-1 |\n| 1.2 | Authority.................................................................................................................1-1 Scope................................................................................................1-1 | Authority.................................................................................................................1-1 Scope................................................................................................1-1 | |\n| 1.3 | Purpose and Audience ................................................................................................................1-1 | Purpose and Audience ................................................................................................................1-1 | |\n| 1.4 | | | |\n| 2."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "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 Forensic Filtering of Cell Phone Protocols provide?"}, {"role": "assistant", "content": "\n\nNISTIR 7516\n\n## Forensic Filtering of Cell Phone Protocols\n\nAurélien Delaitre Wayne Jansen\n\nNISTIR 7516\n\n## Forensic Filtering of Cell Phone Protocols\n\nAurélien Delaitre Wayne Jansen\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nAugust 2008\n\n\n\n## U.S. Department of Commerce\n\nCarlos M. Gutierrez, Secretary\n\nNational Institute of Standards and Technology\n\nJames M. Turner, Deputy Director ii\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Interagency Report discusses ITL's research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Interagency Report 42 pages (2008)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Forensic Filtering of Cell Phone Protocols", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Software Vulnerability Management:\n\nSoftware Vulnerability Management\n\nSoftware Vulnerability Management\n\nThe NISTIR 8011 capability-specific volumes focus on the automation of security control assessment within each individual information security capability. The capability-specific volumes add tangible detail to the more general overview given in NISTIR 8011 Volume 1, providing a template for transition to a detailed, NIST standards-compliant automated assessment. This document, Volume 4 of NISTIR 8011, addresses automating the assessment of security controls that support the software vulnerability management security capability to facilitate the management of risk created by defects present in software on the network. Software vulnerability management, in the scope of this document, focuses on known defects that have been discovered in software in use on a system. The Common Weakness Enumeration (CWE) provides identifiers for weaknesses that result from poor coding practices and have the potential to result in software vulnerabilities. The Common Vulnerabilities and Exposures (CVEs) program provides a list of many known vulnerabilities. Together, CVE and CWE are used to identify software defects and the weaknesses that cause a given defect. Vulnerable software is a key target that attackers use to initiate an attack internally and to expand control."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Vulnerability Management", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\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": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "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 IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\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 (SP) 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 will increasingly use Internet of Things (IoT) devices for the mission benefits they can offer, but care must be taken in the acquisition and implementation of IoT devices. This publication contains background and recommendations to help organizations consider how an IoT device they plan to acquire can integrate into a system."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "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 on Electronic Mail Security provide? (Part 4)"}, {"role": "assistant", "content": "--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| 1.\n| Introduction ......................................................................................................................1-1 1.1 | Authority...................................................................................................................1-1 | Summary..............................................................................................................ES-1 |\n| | 1.2 | Purpose and Scope .................................................................................................1-1 | Summary..............................................................................................................ES-1 |\n| | 1.3 | Audience and Assumptions .....................................................................................1-2 | Summary..............................................................................................................ES-1 |\n| | 1.4 Document Organization | ...........................................................................................1-2 | Summary..............................................................................................................ES-1 |\n| 2."}], "metadata": {"source": "Guidelines on Electronic Mail Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Information System Security Best Practices for UOCAVA-Supporting Systems:\n\nMany jurisdictions make voter registration and ballot request forms available on their web sites, or are willing to e-mail them to voters upon request. Depending on local procedures and state law, some jurisdictions will accept completed voter registration or ballot request forms from voters over e-mail or allow voters to upload scanned forms to web sites. A growing number of jurisdictions are creating web sites that allow voters to fill out a web form to submit updates to their voter registration information. In these cases, proper operational, managerial and technical security controls must be implemented to ensure sensitive personally-identifiable material from voters is kept secure. Computer management entails any modification to the computer that changes the way that the computer operates. Management access control is restricting who can manage the computer to a limited number of known people. For example, on a PC used in a personal work setting, setting the electronic clock back by an hour will have minimal impact on the use of the computer; on a server that is handling requests for electronic ballots, making such a change (even with auditing) could have huge effects on the security of the voting system. Other management tasks can similarly be benign or serious; changes such as rebooting, patching the operating system, limiting the ability of a user to write files over a certain size, or even where DNS resolution information is obtained need to be considered in light of all the operational uses of the computer. Similarly, one might allow certain people rights to change only a few settings on a server, but it is almost impossible to prevent anyone from rebooting a computer if they have physical access to it. Every server has at least one way to manage it, and often has at least a few. Some servers are managed directly on the server themselves, using keyboards and monitors attached directly to the servers."}], "metadata": {"source": "Information System Security Best Practices for UOCAVA-Supporting 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nDigital Identity Guidelines\nAuthentication and Authenticator Management\n\nTemoshok D, Fenton JL, Choong YY, Lefkovitz N, Regenscheid A, Galluzzo R, Richer JP\n(2025) Digital Identity Guidelines: Authentication and Authenticator Management.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special\nPublication (SP) NIST SP 800-63B-4. https://doi.org/10.6028/NIST.SP.800-63B-4"}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to General Access Control Guidance for Cloud Systems:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. 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. 1. Broad network access : Cloud services are available over the network and accessible through standard mechanisms that promote use by heterogeneous thick and thin client platforms (e.g., mobile phones, tablets, laptops, workstations). This raises security concerns with regard to network access. For example, denial of service (DoS) attacks can be launched against a cloud system, rendering its resources unavailable to legitimate users. Thus, AC for network access should be managed. 2. Resource pooling : The computing resources of a cloud system (e.g., storage, memory, processing, network bandwidth) are pooled to serve multiple consumers using a multitenant model (i.e., a single instance of the software and its supporting infrastructure serves multiple consumers) through different physical and virtual resources, each dynamically assigned and reassigned according to consumer demands."}], "metadata": {"source": "General Access Control Guidance for Cloud Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Risk Assessment?"}, {"role": "assistant", "content": "According to Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations:\n\n......................98 |\n| Table 11. Maintenance (MA) ......................................................................................................................98 |\n| Table 12.\nMedia Protection (MP)................................................................................................................99 |\n| Table 13. Physical and Environmental Protection (PE)...............................................................................99 |\n| Table 14. Planning (PL)..............................................................................................................................100 |\n| Table 15. Program Management (PM) .....................................................................................................100 |\n| Table 16. Personnel Security (PS) .............................................................................................................101 |\n| Table 17. PII Processing and Transparency (PT) .......................................................................................102 |\n| Table 18. Risk Assessment (RA) ................................................................................................................102 |\n| Table 19. System and Services Acquisition (SA)........................................................................................103 |\n| Table 20. System and Communications Protection (SC)...........................................................................103 |\n| Table 21. System and Information Integrity (SI) .......................................................................................104 |\n| Table 22. Supply Chain Risk Management (SR).........................................................................................105 |\n| Table 23."}], "metadata": {"source": "Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations", "cmmc_level": "2", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\n## Federal Cybersecurity Awareness Programs\n\n## Federal Cybersecurity Awareness Programs\n\nPrior industry surveys and research studies have revealed that organizational cybersecurity awareness (hereafter shortened to 'security awareness') programs may face a number of challenges, including lack of: leadership support; resources; and staff with sufficient background and skills to implement an effective and engaging program. However, no prior research has explored security awareness programs specifically in the United States (U.S.) government (federal) sector. To address this gap, NIST conducted a two-phase, mixed methods research study to understand the needs, challenges, and practices of federal security awareness programs. This report describes the research background and methodology, along with the characteristics of the participants, organizations, and programs represented in the study. Research results can serve as a resource for federal security awareness professionals, managers, and organizational decision makers to improve and advocate for their organizations' security awareness programs. Results can also inform the development of federal security awareness guidance, policies, sharing forums, and initiatives meant to aid programs in becoming more effective. While focused on the U.S. government, findings may also have implications for organizational security awareness programs in other sectors."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 1_ Overview:\n\n3.1.5 Improves Risk Management by Measuring Security Results More Closely Aligned with Desired Business Results... 3.1.5 Improves Risk Management by Measuring Security Results More Closely Aligned with Desired Business Results\n\nNIST guidance on information security risk stresses the need to focus not just on system-level risk, but also on mission-level risks (SP 800-30 and SP 800-39)."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies:\n\ncipating organizations to accept each other's security assessments in order to reuse information-system resources and/or to accept each other's assessed security posture in order to share information.\n|\n|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Risk Analysis | See risk assessment. |\n| Risk Assessment | The process of identifying risks to organizational operations (including mission, functions, images, and reputation), organizational assets, individuals, other organizations, and the Nation, resulting from the operation of an information system. Part of risk management, incorporates threat and vulnerability analyses, and considers mitigations provided by security controls planned or in place. |\n| Risk Management | The program and supporting processes to manage information security risk to organizational operations (including mission, functions, images, and reputation), organizational assets, individuals, other organizations, and the Nation, and includes: (i) establishing the context for risk-related activities, (ii) assessing risk, (iii) responding to risk once determined, and (iv) monitoring risk over time. |\n| Security Control | A safeguard or countermeasure prescribed for an information system or an organization designed to protect the confidentiality, integrity, and availability of its information and to meet a set of defined security requirements. |\n| Security Policy | A set of criteria for the provision of security services."}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies", "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 Glossary of Key Information Security Terms:\n\nThis publication differs significantly from previous versions of NIST IR 7298. Previous versions contained a subset of basic terms that were most frequently used in NIST publications. This method was valuable, but greater demand and frequent updates to NIST's publication suite has necessitated the adoption of a more flexible solution.\n\n## 3 Feedback & Updates"}], "metadata": {"source": "Glossary of Key Information Security Terms", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Security Property Verification by Transition Model:\n\n3.2.3."}], "metadata": {"source": "Security Property Verification by Transition Model", "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 Physical Protection?"}, {"role": "assistant", "content": "According to PDA Forensic Tools_ an Overview and Analysis:\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 Interagency Report discusses ITL's research, guidance, and outreach efforts in computer security, and its collaborative activities with industry, government, and academic organizations. - Prepare a forensic copy (i.e., an identical bit-for-bit physical copy) of the acquired digital media, while preserving the acquired media's integrity. - Examine the forensic copy to recover information. - Analyze the recovered information and develop a report documenting the incriminating information uncovered. Forensic tools acquire data from a device in one of two ways: physical acquisition or logical acquisition. Physical acquisition implies a bit-by-bit copy of an entire physical store (e.g., a disk drive or RAM chip), while logical acquisition implies a bit-by-bit copy of logical storage objects (e.g. directories and files) that reside on a logical store (e.g., involving several disk drives). The difference lies in the distinction between memory as seen by a process through the operating system facilities (i.e., a logical view), versus memory as seen by the processor and other related hardware components (i.e., a physical view)."}], "metadata": {"source": "PDA Forensic Tools_ an Overview and Analysis", "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 Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations provide? (Part 2)"}, {"role": "assistant", "content": "ions for further research, study, and guidance development. For information on NIST's Cyber Supply Chain Risk Management project, see https://csrc.nist.gov/projects/cyber-supply-chain-risk-management.\n## DISCLAIMER\n\nAny mention of commercial products or organizations is for informational purposes only; it is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the products identified are necessarily the best available for the purpose."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.2.5. 3.2.5. 3.2.5."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog:\n\n| SU - SOFTWARE | UPDATE.................................................................................. 27 |\n|--------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|\n| (UPD) Update Capabilities ............................................................................27 | |\n| (APP) Update Application Support................................................................28 | |\n| CS - CYBERSECURITY STATE AWARENESS..................................................."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "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 Discussion on the Full Entropy Assumption of the SP 800-90 Series provide?"}, {"role": "assistant", "content": "\n\n## NIST Interagency Report NIST IR 8427\n\n## Discussion on the Full Entropy Assumption of the SP 800-90 Series\n\nDarryl Buller Aaron Kaufer Allen Roginsky Meltem Sönmez Turan\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8427.ipd\n\n\n\n## NIST Interagency Report NIST IR 8427\n\n## Discussion on the Full Entropy Assumption of the SP 800-90 Series\n\nDarryl Buller Aaron Kaufer Cybersecurity Directorate National Security Agency\n\nAllen Roginsky Meltem Sönmez Turan\n\nComputer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8427\n\nApril 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": "Discussion on the Full Entropy Assumption of the SP 800-90 Series", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 BowTie – A deep learning feedforward neural network for sentiment analysis:\n\nproducers are competing to discover first: the companies to fix, the hackers to exploit. Patching products changes the game for hackers and slows down their progress. Thus, patching promptly is a way of staying ahead of security breaches. However, patching changes also the environment in which a cryptographic module runs and may also change the module itself, thus invalidating the previously validated configuration. Users who depend on validated cryptography face a dilemma when frequent updates and patches are important for staying ahead of the attackers, but the existing validation process does not permit rapid implementation of these updates while maintaining a validated status because of the slow human-based activities illustrated in Fig. 7."}], "metadata": {"source": "BowTie – A deep learning feedforward neural network for sentiment analysis", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Integrating Cybersecurity and Enterprise Risk Management (ERM):\n\nCybersecurity risk is an important type of risk for any enterprise. Other risks include but are not limited to financial, legal, legislative, operational, privacy, reputational, safety, strategic, and supply chain risks [2]. As part of an ERM program, senior leaders (e.g., corporate officers, government senior executive staff) often have fiduciary and reporting responsibilities that other organizational stakeholders do not, so they have a unique responsibility to holistically manage the combined set of risks, including cybersecurity risk.\n\nCybersecurity risk is one portion of the spectrum of an enterprise's core risks. Appendix A of Playbook: Enterprise Risk Management for the U.S. Federal Government [2] defines numerous risk types, including compliance, cybersecurity ('cyber information security'), financial, legal, legislative, operational, reputational, and strategic. This list can easily be expanded to other risk disciplines, such as safety, privacy, and supply chains that ultimately anchor in ERM. In ERM, enterprises holistically manage the combined set of enterprise risks. 9\n\n- Information regarding the risk itself, such as a detailed risk scenario description and underlying threats, vulnerabilities, assets threatened, risk category, and risk assessment results\n- Roles involved in risk decisions and management (e.g., risk owner, risk manager, action owner for specific activities, stakeholders involved in risk response decisions, contractual agreements for supply chain/external partners)\n- Schedule considerations, such as the date the risk was first documented, the date of the last risk assessment, completion dates for mitigations, and the date of the next expected assessment\n- Risk response decisions and follow-up, including detailed plans, status, and risk indicators"}], "metadata": {"source": "Integrating Cybersecurity and Enterprise Risk Management (ERM)", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook:\n\n| Paraaraoh | | | Pace |\n|-------------|-------------------------------------------------------|-------------------------------------------------------|--------|\n| | c. | Personnel Screening | 3-6 |\n| | d. | Access Protection and Accountability | 3-6 |\n| | e. | Compliance Assurance | 3-6 |\n| | f | Contingency and Disaster Recovery Plans | 3-7 |\n| | g- | Approval of Methodologies | 3-7 |\n| 303 | Risk | Assessment Process | 3-7 |\n| 304 | Protective Measures to Prevent Misuse and Abuse | Protective Measures to Prevent Misuse and Abuse | 3-10 |\n| 305 | Certification | Process | 3-10 |\n| | a. | New or Modified Applications | 3-11 |\n| | b. | Recertifications | 3-12 |\n| 306 | Procedures for Screening Non-Federal Personnel | Procedures for Screening Non-Federal Personnel | 3-13 |\n| | a. | Scope and Applicability | 3-13 |\n| | b. | Objective | 3-13 |\n| | c."}], "metadata": {"source": "National Aeronautics and Space Administration's (NASA) Automated Information Security Handbook", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security Division 2008 Annual Report:\n\n- Develop NIST guides for securing non-national security agency ◆◆ information systems - Issued eighteen NIST Special Publications (SP) covering management, operational and technical security guidance. Collaborated with the Office of the Director of National Intelligence and the Department of Defense to transform the certification and accreditation process for information systems into a common framework for information security across the federal government. - Define minimum information security requirements (manage-◆◆ ment, operational, and technical security controls) for information and information systems in each such category - Issued revision 2 of SP 800-53, Recommended Security Controls for Federal Information Systems, in December 2007. - Identify methods for assessing effectiveness of security require-◆◆ ments - Issued SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems, in June 2008. - Establish performance measures for agency information security ◆◆ policies and practices - Issued revision 1 of SP 800-55, Performance Measurement Guide for Information Security, in July 2008. - Provide assistance to agencies and private sector ◆◆ - Conducted ongoing, substantial reimbursable and non-reimbursable assistance support, including many outreach efforts such as the Federal Information Systems Security Educators' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSM Forum), the Small Business Corner, and the Program Review for Information Security Management Assistance (PRISMA). - Evaluate security policies and technologies from the private ◆◆ sector and national security systems for potential federal agency use - Hosted a growing repository of federal agency security practices, public/private security practices, and security configuration checklists for IT products."}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "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.4 (NIST 3.1.4)?"}, {"role": "assistant", "content": "According to An Introduction to Privacy Engineering and Risk Management in Federal Systems:\n\n3.1.4, available at http://www."}], "metadata": {"source": "An Introduction to Privacy Engineering and Risk Management in Federal Systems", "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 does CMMC require for Planning?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\ndra Wood); Tumult Labs (Gerome Miklau and David Pujol); the United Health Group (Peter Dumont and Ying Zhu); and the U.S. Agency for International Development Chief Data Officer (Brandon Pustejovsky).\nAgencies should consider performing de-identification with trained individuals using software specifically designed for that purpose. While it is possible to perform de-identification with off-the-shelf software like a commercial spreadsheet or financial planning program, such programs typically lack the key functions required for sophisticated de-identification. As a result, they may encourage the use of simplistic de-identification methods, such as deleting columns that contain sensitive data categories and manually searching and removThis may result in a dataset that appears de-identified but still contains significant disclosure risks. 2 ing individual data cells that appear sensitive."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "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 Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\n- -Phase 2a: Planning and Design . In this phase, WLAN network architects specify the technical characteristics of the WLAN solution, such as authentication methods, and related network components, such as firewall rulesets. The WLAN network architects should also conduct a site survey to help determine the architecture of the solution and how the WLAN should be integrated with the existing authentication infrastructure, including PKI. - -Phase 2b: Procurement . This phase involves specifying the number and type of WLAN components that must be purchased, the feature sets they must support (e.g., FIPS-validated encryption modules), and any certifications they must hold (e.g., WPA2 Enterprise). - GLYPH<c=31,font=/HACNND+Webdings> Phase 3: Implementation . In this phase, procured equipment is first configured to meet operational and security requirements, and then installed and activated on a production network, with appropriate event logging enabled. - GLYPH<c=31,font=/HACNND+Webdings> Phase 4: Operations/Maintenance . This phase includes security-related tasks that an organization should perform on an ongoing basis once the WLAN is operational, including patching, periodic security assessment, log reviews, and incident handling. - GLYPH<c=31,font=/HACNND+Webdings> Phase 5 : Disposition. This phase encompasses tasks that occur after a system or its components have been retired, including preserving information to meet legal requirements, sanitizing media that might contain sensitive material, and disposing of equipment properly. Another major problem with shared key authentication is that pre-RSN IEEE 802.11 requires all devices on a WLAN to use the same WEP key or the same small set of keys. This reduces accountability and complicates troubleshooting and incident response efforts."}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "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 Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\nCritical infrastructure is defined in the EO as 'systems and assets, whether physical or virtual, so vital to the United States that the incapacity or destruction of such systems and assets would have a debilitating impact on security, national economic security, national public health or safety, or any combination of those matters.' Due to the increasing pressures from external and internal threats, organizations responsible for critical infrastructure need to have a consistent and iterative approach to identifying, assessing, and managing cybersecurity risk. This approach is necessary regardless of an organization's size, threat exposure, or cybersecurity sophistication today. While the intended outcomes identified in the Functions, Categories, and Subcategories are the same for IT and ICS, the operational environments and considerations for IT and ICS differ. ICS have a direct effect on the physical world, including potential risks to the health and safety of individuals, and impact on the environment. Additionally, ICS have unique performance and reliability requirements compared with IT, and the goals of safety and efficiency must be considered when implementing cybersecurity measures."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\nn the protection mechanisms required by the organization. - o Methods to achieve confidence -what methods the organization uses, would like to use, or have available to achieve the desired confidence.\n- o Addressing evolving protection reguirements of the 1990s -how the organization sees its situation and environment changing over the next few years and how that impacts its protection requirements"}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "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 Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities provide? (Part 5)"}, {"role": "assistant", "content": "develops tests, test methods, reference data, proof of concept implementa/t\\_i.ligaons, and technical analyses to advance the development and produc/t\\_i.ligave use of informa/t\\_i.ligaon technology.\nITL's responsibili/t\\_i.ligaes include the development of management, administra/t\\_i.ligave, technical, and physical standards and guidelines for the cost-e/uniFB00ec/t\\_i.ligave security and privacy of other than na/t\\_i.ligaonal security-related informa/t\\_i.ligaon in federal informa/t\\_i.ligaon systems. The Special Publica/t\\_i.ligaon 800series reports on ITL's research, guidelines, and outreach e/uniFB00orts in informa/t\\_i.ligaon system security, and its collabora/t\\_i.ligave ac/t\\_i.ligavi/t\\_i.ligaes with industry, government, and academic organiza-/t\\_i.ligaons. ## Audience\n\nThe intended audience includes security researchers, so/f\\_t.ligaware and hardware developers, informa/t\\_i.ligaon technology (IT) managers, and IT execu/t\\_i.ligaves. i\n\n1. Introduc/t\\_i.ligaon\n\n. . . . . . . . . ## Table of Contents\n\n. . . . . . . . . . . . . . . | 2. | Current State of the Art . | . . . . . . . . . . . . . | 3 |\n|------|-----------------------------------------|-----------------------------------------------------------------------------|-----|\n| 3. | Bugs Framework Formalism . . . . . | . . . . . . . . . . . . | 5 |\n| | 3.1. | BF Opera/t_i.ligaon . . . . . . . . . . . . | 7 |\n| | 3.2. | BF Bug, Fault, and Weakness . . . . . . . . . . . . . . . . | 8 |\n| | 3.3. | BF Vulnerability . . . . . . . . | 10 |\n| | 3.4. | BF Bug Iden/t_i.liga/uniFB01ca/t_i.ligaon . . . . . . . . . . . . . . . . | 13 |\n| 4. | BF Security Concepts . . | . . . . . . . . . . . . . | 14 |\n| 5. | BF Bugs Models . | . . . . . . . . . . . . . . . . | 16 |\n| | 5.1. | BF Input/Output Check ( INP) Bugs Model . . . . . . | 16 |\n| | 5.2. | BF Memory ( MEM) Bugs Model | 17 |\n| | 5.3."}], "metadata": {"source": "Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Forensics Web Services (FWS) provide? (Part 2)"}, {"role": "assistant", "content": "ndation 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.\n## Acknowledgements\n\nThe authors Anoop Singhal, Murat Gunestas and Duminda Wijesekera would like to thank their colleagues who reviewed drafts of this document and contributed to its development. A special note of thanks goes to Mark Carson, Rick Ayers, Rick Kuhn, Ramaswamy Chandramouli and Karen Scarforne of NIST for serving as reviewers for this document. The authors also acknowledge Elizabeth Lennon for her technical editing and administrative support. ## Abstract\n\nThe advance of Web services technologies promises to have far-reaching effects on the Internet and enterprise networks. Web services based on the eXtensible Markup Language (XML), Simple Object Access Protocol (SOAP), and related open standards, and deployed in Service Oriented Architectures (SOA) allow data and applications to interact without human intervention through dynamic and ad hoc connections. Web services technology can be implemented in a wide variety of architectures, can co-exist with other technologies and software design approaches, and can be adopted in an evolutionary manner without requiring major transformations to legacy applications and databases. Web services are currently a preferred way to architect and provide complex services. This complexity arises due to the composition of new services and dynamically invoking existing services. These compositions create service inter-dependencies that can be misused for monetary or other gains. When a misuse is reported, investigators have to navigate through a collection of logs of the composed services to recreate the attack."}], "metadata": {"source": "Forensics Web Services (FWS)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2:\n\n-  Languages. The SCAP languages provide standard vocabularies and conventions for expressing security policy, technical check mechanisms, and assessment results. The SCAP language specifications are Extensible Configuration Checklist Description Format (XCCDF), Open Vulnerability and Assessment Language (OVAL®), and Open Checklist Interactive Language (OCIL™). -  Reporting formats. The SCAP reporting formats provide the necessary constructs to express collected information in standardized formats. The SCAP reporting format specifications are Asset Reporting Format (ARF) and Asset Identification. Although Asset Identification is not explicitly a reporting format, SCAP uses it as a key component in identifying the assets that reports relate to. -  Enumerations. Each SCAP enumeration defines a standard nomenclature (naming format) and an official dictionary or list of items expressed using that nomenclature. The SCAP enumeration specifications are Common Platform Enumeration (CPE™), Common Configuration Enumeration (CCE™), and Common Vulnerabilities and Exposures (CVE®). -  Measurement and scoring systems. In SCAP this refers to evaluating specific characteristics of a security weakness (for example, software vulnerabilities and security configuration issues) and, based on those characteristics, generating a score that reflects their relative severity. The SCAP measurement and scoring system specifications are Common Vulnerability Scoring System (CVSS) and Common Configuration Scoring System (CCSS). -  Integrity. An SCAP integrity specification helps to preserve the integrity of SCAP content and results. Trust Model for Security Automation Data (TMSAD) is the SCAP integrity specification."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.2", "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 Access Control?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\nFor organizations that process unclassified sensitive information, the availability of a greater variety of trusted products that go beyond C2 in terms of functionality and flexibility is needed. There is a demand to address data integrity in a more direct and user friendly manner. Vendors should consider new mechanisms that directly address discretionary and non~discretionary controls, such as role-based access controls, separation of duties, separation of transactions, and user-oriented least privilege."}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.2 (NIST 3.1.2)?"}, {"role": "assistant", "content": "According to Guide to Integrating Forensic Techniques into Incident Response:\n\n3.1.2 Acquiring the Data... 3.1.2, organizations should determine in advance which actions should be performed by law enforcement officials. 3.1.2 describes the recommended steps for collecting data, including additional actions necessary to support legal or internal disciplinary proceedings."}], "metadata": {"source": "Guide to Integrating Forensic Techniques into Incident Response", "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 guidance does Approximate Matching_ Definition and Terminology provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-168\n\n## Approximate Matching: Definition and Terminology\n\nFrank Breitinger Barbara Guttman Michael McCarrin Vassil Roussev Douglas White http://dx.doi.org/10.6028/NIST.SP.800-168\n\n\n\n## NIST Special Publication 800-168\n\n## Approximate Matching: Definition and Terminology\n\nFrank Breitinger University of New Haven West Haven, CT\n\nDouglas White Barbara Guttman Software and Systems Division Information Technology Laboratory\n\nMichael McCarrin Naval Postgraduate School Monterey, CA\n\nVassil Roussev University of New Orleans New Orleans, LA\n\nhttp://dx.doi.org/10.6028/NIST.SP.800-168\n\nMay 2014\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Under Secretary of Commerce for Standards and Technology and Director\n\n## Authority\n\nThis publication has been developed by National Institute of Standards and Technology (NIST) to further its statutory responsibilities under the Federal Information Security Management Act (FISMA), Public Law (P.L.) 107-347. NIST is responsible for developing information security standards and guidelines, including minimum requirements for Federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate Federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130, Section 8b(3), Securing Agency Information Systems , as analyzed in Circular A­ 130, Appendix IV: Analysis of Key Sections . Supplemental information is provided in Circular A-130, Appendix III, Security of Federal Automated Information Resources . Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on Federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Approximate Matching_ Definition and Terminology", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guidelines on Security and Privacy in Public Cloud Computing:\n\nOrganizations should employ appropriate security management practices and controls over cloud computing. Strong management practices are essential for operating and maintaining a secure cloud computing solution. Security and privacy practices entail monitoring the organization's information system assets and assessing the implementation of policies, standards, procedures, controls, and guidelines that are used to establish and preserve the confidentiality, integrity, and availability of information system resources. Opportunities for improved security also benefit privacy. That is, effective privacy can exist only upon a sound foundation of information security. However, privacy, just as security, has broad organizational, operational, and technical implications. While some aspects of privacy are closely related to the confidentiality, integrity, and availability objectives of security, other aspects are not. Instead, they involve important privacy-related principles and considerations that are addressed in law, regulations, and OMB guidance [CIO10b]. ▪ Mechanism Cracking. WiFi Protected Access (WPA) Cracker, a cloud service ostensibly for penetration testers, is an example of harnessing cloud resources on demand to break a cryptographic cipher and determine the encrypted password used to protect a wireless network. Through this service, a task that would take five days to run on a single computer can be accomplished in only 20 minutes on a cluster of 400 virtual machines [Rag09]. Because cryptography is used widely in authentication, data confidentiality and integrity, and other security mechanisms, these mechanisms become, in effect, less effective with the availability of cryptographic key cracking cloud services. Both cloud-based and traditional types of systems are possible targets."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "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 Communications Protection?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n| | 3.6.2. | Cryptographic Key Storage . . . . . . . . . . . . . . . . . . . . . 27 |\n|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|\n| 3.7. | 3.6.3. Software Attestations . . . . . . Authentication and Attribute Disclosure . | . . . . . . . . . . . . . . . . . 27 . . . . . . . . . . . . . . . . . 27 |\n| 3.8. | RP Subscriber Accounts . . . . . . . . . | . . . . . . . . . . . . . . . . . 28 |\n| | 3.8.1. Account Linking . . . . . . . . . . . . . . . . | 29 |\n| | . . . . . . . . . . 3.8.2. Account Resolution . . . . . . . . . . . . . . . . . . . . . . . . 3.8.3. Alternative Authentication Processes . . . . . . . . . . . . . . . Authenticated Sessions at the RP . . . . . . . . . . . . . . . . . . . . . | 30 30 31 |\n| | 3.13.2. Signed Assertion . . . . . . . . . . . . . . . . . . . . . . . . . . . | . . . . . . . . . . . . . |\n| 3.9. 3.11. | 3.10.2. Sharing Information Between CSPs Identity Attributes . . . . . . . . . . . . 3.13.3. Encrypted Assertion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | . . . . . . . . . . . . . . . . 34 . . . . . . . . . . . . . . . 42 |\n| | 3.12.1. Attribute Bundles . . . . . . . . | 32 . . . . . . . . . . . . . . . |\n| 3.10. | Privacy Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3.10.1. Transmitting Subscriber Information . . . . . . . . . . . . | . . . . . . 33 |\n| 3.12. | 3.11.1. Protection From Assertion Injection Attacks . ."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio:\n\n............................................................... 1 | Executive Summary.................................................................................................................\n1 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| | Introduction ...................................................................................................................... | 5 |\n| 1.1 | Purpose and Scope.................................................................................................... | 5 |\n| 1.2 | Document Structure.................................................................................................... | 6 |\n| Introduction to ICTRM and Challenges with ERM Integration......................................."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guidelines on PDA Forensics:\n\nThe object store refers to three types of persistent storage supported by Windows CE within the Operating System Layer: file system, registry, and property databases. Standard Win32 functions provide access to files and the registry, while new Windows CE-specific API functions provide access to property databases and certain registry features. The subset of Win32 and other Microsoft APIs implemented in Pocket PC allows a system to fulfill the requirements of an embedded application, yet keep the programmability similar to that of Windows PCs. The maximum size of the object store is 256MB in Windows CE. The object store is built on an internal heap that resides in RAM, ROM, or both. The internal heap provides a transaction model that uses logging to ensure the integrity of the object store data. documentation features. 21 Although more widely used for examining PCs, EnCase also supports Palm OS devices. Currently, support for Pocket PC is not available, but the ability to import a data dump of Linux-based PDAs exists. EnCase allows for the creation of a complete physical bit-stream image of a Palm OS device. Throughout the process, the integrity of the bit-stream image is continually verified by CRC (Cyclical Redundancy Check) values, which are calculated concurrent to acquisition. The resulting bit-stream image, called an EnCase evidence file, is mounted as a read-only file or 'virtual drive' from which EnCase proceeds to reconstruct the file structure using the logical data in the bit-stream image. This allows the examiner to search and examine the contents of the device using either a logical or physical perspective. The above sets of principles aim to ensure the integrity and accountability of digital evidence through its entire life cycle. Proper handling of evidence is always vital for it to be admissible in judicial proceedings."}], "metadata": {"source": "Guidelines on PDA Forensics", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Federal S_MIME V3 Client Profile provide?"}, {"role": "assistant", "content": "NIST Special Publication 800-49\n\n\n\n## Federal S/MIME V3 Client Profile\n\nC. Michael Chernick\n\n## C O M P U T E R S E C U R I T Y\n\nNovember 2002\n\n## NIST Special Publication 800-49 Federal S/MIME V3 Client\n\n## Profile\n\n## Recommendations of the National Institute of Standards and Technology\n\n## C. Michael Chernick\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\n## November 2002\n\n\n\nU.S. Department of Commerce\n\n## Donald L. Evans, Secretary\n\nTechnology Administration\n\n## Phillip J. Bond, Under Secretary of Commerce for Technology\n\nNational Institute of Standards and Technology\n\n## Arden L. Bement, Jr., Director\n\n## Reports on Information Security Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analysis to advance the development and productive use of information technology. ITL's responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL's research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Federal S_MIME V3 Client Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Advanced Encryption Standard (AES):\n\nThe block ciphers AES-128, AES-192, and AES-256 differ in three respects: 1) the length of the key; 2) the number of rounds, which determines the size of the required key schedule; and 3) the specification of the recursion within KEYEXPANSION(). For each algorithm, the number of rounds is denoted by Nr , and the number of words of the key is denoted by Nk . (The number of words in the state is denoted by Nb for Rijndael in general; in this Standard, Nb = 4.) The specific values of Nk , Nb , and Nr are given in Table 3. No other configurations of Rijndael conform to this Standard.\n\nThe first step (Line 2) is to copy the input into the state array using the conventions from Sec. 3.4. After an initial round key addition (Line 3), the state array is transformed by Nr applications of the round function (Lines 4-12); the final round (Lines 10-12) differs in that the MIXCOLUMNS() transformation is omitted. The final state is then returned as the output (Line 13), as described in Section 3.4.\n\nTo implement INVCIPHER(), the transformations in the specification of CIPHER() (Section 5.1) are inverted and executed in reverse order. The inverted transformations of the state - denoted by INVSHIFTROWS(), INVSUBBYTES(), INVMIXCOLUMNS(), and ADDROUNDKEY() - are described in Sections 5.3.1-5.3.4."}], "metadata": {"source": "Advanced Encryption Standard (AES)", "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 CMVP Documentation Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759:\n\nConformance testing; Cryptographic Module Validation Program; CMVP; FIPS 140 testing; FIPS 140; ISO/IEC 19790; ISO/IEC 24759 testing requirement; vendor evidence; vendor documentation.\n\nThis document is focused toward the vendors, testing labs, and CMVP for the purpose of addressing issues in ISO/IEC 24759, Test requirements for cryptographic modules .\n\nFederal Information Processing Standard (FIPS) 140-3 documentation requirements are specified in ISO/IEC 19790. This document specifies any additional requirements specified by the Cryptographic Module Validation Program (CMVP) for evidence that vendors provide to a Cryptographic and Security Testing Laboratory (CSTL) to demonstrate conformity. Unless otherwise modified in this document, the test requirements are specified in ISO/IEC 24759."}], "metadata": {"source": "CMVP Documentation Requirements_ CMVP Validation Authority Updates to ISO_IEC 24759", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Cybersecurity of Genomic Data:\n\n| Introduction....................................................................................................................1 | Introduction....................................................................................................................1 | Introduction....................................................................................................................1 | |-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | | Cybersecurity and Privacy Concerns.........................................................................1 | | | | Document Scope and Goals......................................................................................2 | | | Background....................................................................................................................3 | Background....................................................................................................................3 | Background....................................................................................................................3 | | | Genomic Information Lifecycle | ..................................................................................3 | | | Next Generation Sequencing.....................................................................................4 | | | | Variant Calling | ...........................................................................................................4 | | | Genome Editing.........................................................................................................5 | | | | Direct-to-Consumer Testing.......................................................................................5 | | | | The Characteristics of Genomic Data........................................................................6 | | | | Balance Between Benefits and Risks for Uses of Genomic Information | ...................7 | | Challenges and Concerns Associated with Handling Genomic Information...........9 | Challenges and Concerns Associated with Handling Genomic Information...........9 | Challenges and Concerns Associated with Handling Genomic Information...........9 | | | Potential National Security Concerns ........................................................................9 | | | 3.2."}], "metadata": {"source": "Cybersecurity of Genomic Data", "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 Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity” provide? (Part 4)"}, {"role": "assistant", "content": "uct security officers and security architects at IoT product manufacturers and those in their supply chain; cybersecurity test and evaluation experts; and other stakeholders in the IoT product market.\nThis publication may also help customers or integrators of IoT products who are adopting IoT technologies in their residence or business, especially small business networks, as well as organizations concerned with conformity assessment of IoT products to published guidance. ## Table of Contents\n\n| Introduction.........................................................................................................................1 | Introduction.........................................................................................................................1 | Introduction.........................................................................................................................1 |\n|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| Appendix | A. | Poll Results ......................................................................................................16 |\n| | B."}], "metadata": {"source": "Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Security Assessment?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\nion . . . . . . . . . . | 85 | |\n| 7.2 Federation Assurance Level . . . . . . . . . . . . | 85 | |\n| 7.3 Benefits of Federation . . . . . . . . . . . . . | 86 | |\n| Appendix A.\nPIV Validation, Certification, and Accreditation | 87 | |\n| A.1 Accreditation of PIV Card Issuers and Derived PIV Credential Issuers | 87 | |\n| A.2 Application of Risk Management Framework to IT Systems | 87 | |\n| A.3 Conformance Testing of PIV Card Application and | 88 | |\n| A.4 Cryptographic Testing and Validation . . . . . . . . . . . . . . | 88 | |\n| A.5 FIPS 201 Evaluation Program . . . . . . . . | 89 | |\n| Appendix B. PIV Object Identifiers and Certificate Extension | 90 | |\n| B.1 PIV Object Identifiers . . . . . . . . . . . . . . . . | 90 | |\n| | 92 | |\n| Appendix C. Glossary of Terms, Acronyms, and Notations | 93 | |\n| C.1 Glossary of Terms . . . . . . . . . . . . . | 93 | |\n| C.2 Acronyms and Abbreviations . . . . . . . . . . . . . C.3 Notations . . . . . . . . . . . . . . . . . . . . . . . | 102 | |\n| | 109 | |\n| Appendix D. References . . . . . | 110 | |\n| Appendix E. Revision History . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.6 (NIST 3.1.6)?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\n\n3.1.6 Arm RME and Debug, Trace, Profiling, and Performance Monitoring Protection\n\nArm systems include extensive features to support debugging, tracing, and profiling."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "nist_control": "3.1.6", "cmmc_practice_id": "AC.L2-3.1.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Considerations for Remote Electronic UOCAVA Voting:\n\nThis document has been prepared by the National Institute of Standards and Technology (NIST) and describes research in support military and overseas voting for the Election Assistance Commission and the Technical Guidelines Development Committee. It does not represent a consensus view or recommendation from NIST, nor does it represent any policy positions of NIST.\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 organizations 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, organizations may wish to closely follow the development of these new publications by NIST.\n\nThe Election Assistance Commission (EAC) requested that the National Institute of Standards and Technology (NIST) research technologies to improve uniformed and overseas United States citizens' ability to vote, as required by the Uniformed and Overseas Citizens Absentee Voting Act (UOCAVA) [1]. Additionally, the Help America Vote Act of 2002 (HAVA) requires the Technical Guidelines Development Committee, with technical support from NIST, to study remote access voting, including voting over the Internet [2]. This report contains the results of NIST's research into threats and security technologies related to remote electronic voting for overseas and military voters."}], "metadata": {"source": "Security Considerations for Remote Electronic UOCAVA Voting", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\n\n5 |\n| | 3.2 The Chain of Trust | (CoT)................................................................................ 6 |\n| | 3.3 | Supply Chain Protection ................................................................................."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\n3.3.4 KAS2-bilateral-confirmation... 3.3.4. 3.3.4 can be used to provide assurance to a key-pair owner acting as either party U or party V that both parties are in possession of the correct private key; i."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "nist_control": "3.3.4", "cmmc_practice_id": "AU.L2-3.3.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Foundational Cybersecurity Activities for IoT Device Manufacturers support CMMC certification?"}, {"role": "assistant", "content": "According to Foundational Cybersecurity Activities for IoT Device Manufacturers:\n\n## NISTIR 8259\n\n## Foundational Cybersecurity Activities for IoT Device Manufacturers\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.8259\n\n\n\n## NISTIR 8259\n\n## Foundational Cybersecurity Activities\n\n## for IoT Device Manufacturers\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.8259\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 8259 36 pages (May 2020)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8259\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": "Foundational Cybersecurity Activities for IoT Device Manufacturers", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Security Recommendations for Server-based Hypervisor Platforms:\n\n- Hypervisor host user account management\n- Hypervisor host authentication and access control\n- Routine administration of Host OS (e.g., keeping patches current)\n- Routine administration of Guest OS\n- Security of Guest OSs running on VMs\n- Security of Applications/Services running on VMs\n\nConfiguration changes, module version changes, and patches affect the content of the hypervisor platform components such as BIOS, hypervisor kernel, and back-end device drivers running in the kernel. To ensure that each of these components that are part of the hypervisor stack can be trusted, it is necessary to check their integrity through a hardware-rooted attestation scheme that provides assurance of boot integrity. Checking integrity is done by cryptographically authenticating the hypervisor components that are launched. This authentication verifies that only authorized code runs on the system. Specifically, in the context of the hypervisor, the assurance of integrity protects against tampering and low-level targeted attacks such as root kits. If the assertion of integrity is deferred to a trusted third party that fulfills the role of trusted authority, the verification process is known as trusted attestation . Trusted attestation provides assurance that the code of the hypervisor components has not been tampered with. In this approach, trust in the hypervisor's components is established based on trusted hardware. In other words, a chain of trust from hardware to hypervisor is established with the initial component called the root of trust . This service can be provided by a hardware/firmware infrastructure of the hypervisor host that supports boot integrity measurement and the attestation process. In short, a measured launch environment (MLE) is needed in the hypervisor host."}], "metadata": {"source": "Security Recommendations for Server-based Hypervisor Platforms", "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 Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\nAs described in Section 2, prioritization and response will take place based on an analysis of risk scenarios to determine the likelihood that a threat source will act, that a vulnerability does or will exist and that an asset will experience an undesirable effect that impacts objectives. Assets are not limited to technology and include any resource that helps to achieve mission objectives (e.g., people, facilities, critical data, intellectual property, and services). By considering this information with other details from throughout the enterprise, stakeholders can review and monitor risk management to ensure that performance is aligned with enterprise strategy and direction. Because all risk is dynamic, monitoring also enables ongoing adjustments to risk appetite, risk identification methods, and risk response. A key challenge for risk managers is the confusion caused by common risk terms being used for divergent tasks. When considering the application of risk management processes in different contexts, communication among stakeholders may require additional information or clarification about activities. For example, even the meaning of the term control can vary depending on the context in which that term is used. OMB A-123 states that internal controls 'are tools to help program and financial managers achieve results and safeguard the integrity of their programs.' Internal controls provide leaders and managers with methods to help reasonably ensure the achievement of enterprise objectives related to ope rations, reporting, and compliance. As the enterprise's leadership establishes an environment by which those internal controls are enacted (the 'control environment'), they also perform a risk assessment to identify conditions that may prevent the effective application of those internal controls."}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Building a Cybersecurity and Privacy Learning Program:\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\nEnsuring that a federal organization's workforce is aware of and prepared to respond appropriately and effectively to cybersecurity and privacy risks is an important effort that requires a strategic approach based on thoughtful planning, resource considerations, and leadership-driven decision-making. This long-awaited update to the 2003 NIST Special Publication (SP) 800-50, Building an Information Technology Security Awareness and Training Program, provides guidance to create and manage a program that includes cybersecurity and privacy awareness campaigns, role-based training, and other workforce education programs. These programs combine to create an overall Cybersecurity and Privacy Learning Program (CPLP) that is part of a larger organizational effort to reduce cybersecurity and privacy risks. The resulting CPLP supports federal requirements and incorporates industry-recognized best practices for risk management.\n\nCPLPs must have actively managed plans throughout their life cycles, which requires attention and adjustment over time. CPLP managers should carefully and thoughtfully outline, discuss, review, and document the CPLP's goals and available options. When the owners of the organization's CPLP adopt an effective strategy and develop a proper planning approach with measurement and feedback throughout the year, the entire organization remains connected to"}], "metadata": {"source": "Building a Cybersecurity and Privacy Learning Program", "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 AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n3.1.1, 3."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface:\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": "Interfaces for Personal Identity Verification_ Part 3 – PIV Client Application Programming Interface", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry:\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. - -Create explicit collaborative roles, structures, and processes for supply chain, cybersecurity, product security, physical security, and other relevant functions. - -Integrate cybersecurity considerations into the system and product life cycle. - -Determine supplier criticality by using industry standards and best practices. - -Mentor and coach suppliers to improve their cybersecurity practices. - -Include key suppliers in contingency planning (CP), incident response (IR), and disaster recovery (DR) planning and testing. - -Use third-party assessments, site visits, and formal certification to assess critical suppliers. Today, organizations increasingly rely on an array of suppliers to support the organization's critical functions. This trend has accelerated over the last decade and is expected to continue accelerating. Globalization, outsourcing, and digitization contribute to this trend. Suppliers have their own suppliers who, in turn, have their own suppliers, creating extended supply chains and entire supply ecosystems. All organizations rely on acquiring products and services, and most organizations also supply products and services to other organizations."}], "metadata": {"source": "Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry", "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 Guide to Information Technology Security Services provide? (Part 4)"}, {"role": "assistant", "content": "Phase 3: Solution -decision makers evaluate potential solutions, develop the business case and specify the attributes of an acceptable service arrangement solution from the set of available options.\n- ƒ Phase 4: Implementation -the organization selects and engages the service provider, develops a service arrangement, and implements the solution. - ƒ Phase 5: Operations -the organization ensures operational success by consistently monitoring service provider and organizational security performance against identified requirements, periodically evaluating changes in risks and threats to the organization and ensuring the organizational security solution is adjusted as necessary to maintain an acceptable security posture. - ƒ Phase 6: Closeout -the organization ensures a smooth transition as the service ends or is discontinued. This guide describes a life cycle that provides a context to assist organizations with managing the myriad issues surrounding IT security services. However, the guide does not prescribe or recommend any specific IT security service, IT security service arrangement, IT security service agreement, or IT security service provider. Each organization must perform its own analysis of its needs and assess, select, implement, and oversee the IT security service to best address its needs. The Guide should be used in conjunction with other NIST Special Publications (SP) that focus on procurement of IT systems, including NIST SP 800-64, Security Considerations in the Information System Development Life Cycle , and NIST SP 800-36: Guide to Selecting Information Technology Security Products . NIST SP 800-55, Security Metrics Guide for Information Technology Systems will help organizations understand the importance of using metrics and developing a metrics program. Other NIST special publications may be helpful in providing information on specific services and technologies."}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc. provide? (Part 4)"}, {"role": "assistant", "content": "tment of Homeland Security's Information and Communications Technology Supply Chain Risk Management Task Force and the U.S. Customs and Border Protection's Customs-Trade Partnership Against Terrorism.\nThese programs encourage Palo Alto Networks' suppliers and the broader security community to develop robust supply chain and cybersecurity practices. - Contract manufacturers simplify cyber supply chain risk management. Managing thousands of supplier relationships is challenging for organizations at every maturity level. Palo Alto Networks leverages established contract manufacturers with demonstrably diligent cybersecurity and supplier risk management programs. \n\n## Organizational Approach to Supply Chain Risk and Cybersecurity\n\nGiven Palo Alto Networks' role as a cybersecurity vendor, the company is subject to intense scrutiny from potential customers and is a target for a variety of threat actors. Recognizing that a product security incident could have an enormous impact on customers, Palo Alto Networks considers cybersecurity and product integrity an implicit corporate mandate. All products are subject to the company's end-to-end product security framework (E2E Framework). The framework is designed to provide defense in depth for each stage of the product lifecycledesign, sourcing, manufacturing, fulfilment, and service. Each stage is independently evaluated to determine security risks, and domain experts select relevant public standards and best practices to target those risks. Selected standards include the Federal Information Processing Standards (FIPS) i , Common Criteria ii , and the United Kingdom's Commercial Product Assurance (CPA) iii . The E2E Framework is governed by the security council, which is composed of cross-functional senior management from product engineering, product line management, information security, product security, supply chain risk and compliance (SCRC), facility safety and security, and legal."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.1.3. 3.1.3). 3.1.3) should be used."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to General Access Control Guidance for Cloud Systems:\n\nAC policies to be stored and evaluated on the SaaS provider's side. This approach might result in disclosing sensitive data required for evaluating the AC policies to the SaaS provider.\nTherefore, methods for enforcing authorization in the SaaS provider while not disclosing sensitive access control data to the SaaS provider should be considered. Federated authorization [36] is an efficient technique that utilizes a middleware layer to transfer the management of access control policies from the SaaS provider to the consumer side and enforce policies on the SaaS applications without disclosing sensitive data required for evaluating the policies."}], "metadata": {"source": "General Access Control Guidance for Cloud 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 Foundations of a Security Policy for Use of the National Research and Educational Network provide? (Part 4)"}, {"role": "assistant", "content": "cy Interim National Research and Education Network (IINREN). Other security policies and provisions should be expected as this evolves to national and international information networks in the future.\nThe draft policy outlined in the report is considered a level 1 policy in a theoretical hierarchy of policies. This hierarchy ranges from information technology codes of ethics through a number of refined levels of policies down to implementation specifications for security mechanisms, procedures and protocols that support and enforce the policies. Future research is planned to explore this range of policies in a number of security domains that can be defined within a broad distributed network. Dennis K. Branstad, Ph.D. NIST Fellow Project Advisor\n\n## Executive Summary\n\nThe National Research and Education Network (NREN) is an integral part of the planned HighPerformance Computing and Communication (HPCC) infrastructure that will extend throughout the scientific, technical and education communities. The projected vision is one of desks and laboratory benches as entry points to a nation-wide electronic network of information technologies with shared access to services and resources such as high-performance computing systems, specialized software tools, databases, scientific instruments, digital libraries, and other research facilities. The problem of computer and network information security (one of the major computing issues of the day), will be complicated by the diversity of requirements as the NREN is designed, developed, and operated in collaboration with potential users in government, industry, research laboratories, and educational institutions. One major impediment to improved security is the lack of a clearly stated security policy for general computing. In recognition of this problem, national organizations are beginning to develop and publish codes of ethics for the use of computers."}], "metadata": {"source": "Foundations of a Security Policy for Use of the National Research and Educational Network", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Advanced Encryption Standard (AES) provide? (Part 3)"}, {"role": "assistant", "content": "al agencies may also use alternative methods that NIST has indicated are appropriate for this purpose. This Standard may be adopted and used by non-Federal Government organizations. 7. Specifications.\nFederal Information Processing Standard (FIPS) 197, Advanced Encryption Standard (AES) (affixed). 8. Implementations. The algorithm specified in this Standard may be implemented in software, firmware, hardware, or any combination thereof. The specific implementation may depend on several factors, such as the application, the environment, the technology used, etc. The algorithm shall be used in conjunction with a FIPS-approved or NIST-recommended mode of operation. Object Identifiers (OIDs) and any associated parameters for AES used in\n\nthese modes are available at the Computer Security Objects Register (CSOR), located at https://csrc.nist.gov/projects/csor. NIST has developed a validation program to test implementations for conformance to the algorithms in this Standard. Information about the validation program is available at https: //nist.gov/cmvp. Examples for each key size are available at https://csrc.nist.gov/projects/aes. 9. Implementation Schedule. This Standard became effective on May 26, 2002. 10. Patents. Implementations of the algorithm specified in this Standard may be covered by U.S. and foreign patents. 11. Export Control. Certain cryptographic devices and technical data regarding them are subject to federal export controls. Exports of cryptographic modules implementing this Standard and technical data regarding them must comply with all federal laws and regulations and must be licensed by the Bureau of Industry and Security of the U.S. Department of Commerce. Information about export regulations is available at https://www.bis.doc.gov. 12. Qualifications. NIST will continue to follow developments in the analysis of the AES algorithm. As with its other cryptographic algorithm standards, NIST will formally reevaluate this Standard every five years."}], "metadata": {"source": "Advanced Encryption Standard (AES)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.3 (NIST 3.5.3)?"}, {"role": "assistant", "content": "According to Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies:\n\n3.5.3 Government-wide Responsibilities\n\nThe following provisions are directed by Section 6, 'Government-wide Responsibilities."}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies", "cmmc_level": "all", "nist_control": "3.5.3", "cmmc_practice_id": "IA.L2-3.5.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to BIOS Protection Guidelines:\n\nsystem BIOS without direct involvement from the user. 3. Rollback: System BIOS implementations that authenticate updates before applying them may also check version numbers during the update process.\nIn these cases, the system BIOS may have a special update process for rolling back the installed firmware to an earlier version. For instance, the rollback process might require the physical presence of the user. This mechanism guards against attackers flashing old firmware with known vulnerabilities. 4. Manual Recovery: To recover from a corrupt or malfunctioning system BIOS, many computer systems provide mechanisms to allow a user with physical presence during the boot process to replace the current system BIOS with a known good version and configuration. 5. Automatic Recovery: Some computer systems are able to detect when the system BIOS has been corrupted and recover from a backup firmware image stored in a separate storage location from the primary system BIOS (e.g., a second flash memory chip, a hidden partition on a hard drive)."}], "metadata": {"source": "BIOS Protection Guidelines", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs:\n\nmation about an exploit requires human effort that can be large. New techniques are needed to automatically get the exploit information for doing security analysis of enterprise networks.\n- Attack graphs for networks with several hosts can contain cycles. These cycles need to be treated properly in security risk analysis. In [25, 34], some preliminary work on how to detect and handle such cycles has been done. Assuming monotonicity in the acquisition of network privileges, such cycles should be excluded in doing the security risk analysis using attack graphs. Handling cycles correctly is a key challenge in this work. - CVSS scores do not have a fine granularity. Currently the scores are coarse-grained in terms of High, Medium, and Low. A more precise scoring system will improve the overall results of security risk analysis. - New techniques are needed to model zero-day vulnerabilities about which we have no prior knowledge or experience. New techniques need to be developed for security risk analysis of networks against potential zero-day attacks. We have some preliminary results on modeling zero day attacks [35]."}], "metadata": {"source": "Security Risk Analysis of Enterprise Networks Using Probabilistic Attack Graphs", "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 CA.L2-3.12.1 (NIST 3.12.1)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n3.12.1. 3.12.1. 3.12.1."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "nist_control": "3.12.1", "cmmc_practice_id": "CA.L2-3.12.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\n- Endpoint: An Endpoint is the target of a posture assessment. Collection applications will collect software inventory, configuration settings, and other endpoint posture and publish this posture to Posture Collection Servers using standardized protocols and interfaces. These standards will enable Endpoints to be monitored and for changes in posture to be reported automatically. These standards will also allow Posture Collection Servers to query an Endpoint's posture when new or refreshed posture information is required. The initial release of SCAP 2.0 will define protocol requirements for desktops, laptops, and servers; however, all endpoint types are in scope for SCAP v2. Later revisions will define requirements for other endpoint types (e.g., network devices, mobile devices, IoT devices). - Posture Collection Server: This server is responsible for efficiently coordinating the collection of posture from multiple Endpoints. Posture collected from an Endpoint will be published by the Posture Collection Server to the Configuration Management Database (CMDB) where it can then be accessed by other tools. This reduces duplicate posture collection and load on Endpoints that have constrained capabilities, that are under significant load, or that have strict performance requirements. The Posture Collection Server acts as a point of integration for access control and for standardized management protocols including Network Endpoint Assessment (NEA), the Simple Network Management Protocol (SNMP), the Network Configuration Protocol (NETCONF), and mobile device management (MDM) protocols. - Posture Evaluator: By decoupling collection and evaluation and creating standardized interfaces, SCAP v2 enables the distribution of Posture Evaluator service instances across the network. A Posture Evaluator retrieves previously collected posture from a CMDB and requests new posture collection from Posture Collection Servers."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Personnel Security?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. 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\nAs subject attributes may be provisioned by different authorities (e.g., human resources , security , organization leadership , etc.), methods for obtaining authoritative data must be regulated. For example, only security authorities should be able to provision and assert clearance attributes and attribute values based on authoritative personnel clearance information; an individual should not be able to alter his or her own clearance attribute value. Other subject attributes may involve the subject's current tasking, physical location, and the device from which a request is sent. Processes need to be developed to assess and assure the quality of such subject attribute data."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Security for Full Virtualization Technologies:\n\nss method is just username and password, but some bare metal hypervisors offer additional controls such as hardware token-based authentication to grant access to the hypervisor's management interface.\nOn some systems, there are different levels of authorization, such as allowing some users to view logs but not be able to change any settings or interact directly with the guest OSs. These view-only user accounts allow auditors and others to have sufficient access to meet their needs without reducing overall security."}], "metadata": {"source": "Guide to Security for Full Virtualization Technologies", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters:\n\n## Conformance Testing\n\nConformance testing for implementations of this Recommendation will be conducted within the framework of the Cryptographic Algorithm Validation Program (CAVP) and the Cryptographic Module Validation Program (CMVP). The requirements of this Recommendation are indicated by the word ' shall .' Some of these requirements may be out of scope for CAVP or CMVP validation testing and are thus the responsibility of entities using, implementing, installing, or configuring applications that incorporate this Recommendation."}], "metadata": {"source": "Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\nAlthough the focus of [ISO 15288] is systems and software engineering processes, operational\nresilience, which includes cyber resiliency for systems that include or depend on cyber resources,\nis addressed indirectly by requiring organization-wide commitment, resources, practices, and\nprocesses. The interacting elements in the definition of a system include layers of resilience in\nhardware, software, data, information, humans, processes, procedures, facilities, materials, and\nnaturally occurring physical entities. This is important because if the organization’s missions or\nbusiness functions require sustainability during perturbations, disruptions, disturbances, or\ncyber-attacks, then operational resilience practices and procedures must be applied to all of the\nsystem’s assets. It would be of limited value to have resilience measures implemented in the\nsoftware architecture if there is no redundancy and survivability in the hardware, if the\ncommunications networks are fragile, if critical personnel are not available (e.g., in a natural\ndisaster or inclement weather) to operate and maintain the system, or if there are no facilities\navailable for producing the organization’s products and/or services. “Providing satisfactory security controls in a computer system is in itself a system design problem. A\ncombination of hardware, software, communications, physical, personnel and administrative-\nprocedural safeguards is required for comprehensive security. In particular, software safeguards\nalone are not sufficient.”\n\nAn adversary that possesses sophisticated levels of expertise and\nsignificant resources that allow it to create opportunities to\nachieve its objectives by using multiple attack vectors including,\nfor example, cyber, physical, and deception."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nsential for patient safety in emergency conditions from patient personally identifiable information/data to allow different authentication and access control mechanisms to apply to each group of data.\nAlternately, identifying different modes of operation (such as home health setting versus open environment versus emergency situation) to allow the IMD to apply different authentication and access control mechanisms in different modes."}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile:\n\n- NIST research and publications on trustworthy and responsible AI, including the Artificial Intelligence Risk Management Framework (AI RMF 1.0) [2], Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations [3], Towards a Standard for Identifying and Managing Bias in Artificial Intelligence [4], and the Dioptra experimentation testbed for security evaluations of machine learning algorithms [5]. - NIST's Secure Software Development Framework (SSDF) Version 1.1 [6], which is a set of fundamental, sound, and secure software development practices. It provides a common language to help facilitate communications among stakeholders, including software producers and software acquirers. The SSDF has also been used in support of EO 14028, Improving the Nation's Cybersecurity [7], to enhance software supply chain security. - NIST general cybersecurity resources, including The NIST Cybersecurity Framework (CSF) 2.0 [8], Security and Privacy Controls for Information Systems and Organizations [9], and Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations [10]. - AI model developers, AI researchers, AI system developers, and secure software practitioners from industry and government with expertise in the unique security challenges of AI models and the practices for addressing those challenges. This expertise was primarily captured through NIST's January 2024 workshop, where speakers and attendees shared suggestions for adapting secure software development practices and tasks to accommodate the unique aspects of AI model development and the software leveraging them. AI model producers, AI system producers, AI system acquirers, and others can use the SSDF to foster their communications regarding secure AI model development throughout the software development life cycle."}], "metadata": {"source": "Secure Software Development Practices for Generative AI and Dual-Use Foundation Models_ An SSDF Community Profile", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Computer Security Division 2009 Annual Report:\n\nThe Computer Security Division (CSD), a component of NIST's Information Technology Laboratory (ITL), provides standards and technology to protect information systems against threats to the confidentiality, integrity, and availability of information and services. During Fiscal Year 2009 (FY2009), CSD continued its standards development and cybersecurity outreach activities and carried out an expanded research agenda designed to develop and implement high-quality, cost-effective mechanisms needed to improve information security and privacy across the federal government and throughout the national and international information security community. CSD worked with federal partners to establish a unified framework for information security across the federal government. This initiative is resulting in greater standardization and more consistent and cost-effective security for all federal information systems. We also invite public and private organizations to submit their information security practices to be considered for inclusion on the list of practices maintained on the website. Policies and procedures may be submitted to us in any area of information security, includ- ing accreditation, audit trails, authorization of processing, budget planning and justification, certification, contingency planning, data integrity, disaster planning, documentation, hardware and system maintenance, identification and authentication, incident handling and response, life cycle, network security, personnel security, physical and environmental protection, production input/ output controls, security policy, program management, review of security controls, risk management, security awareness training and education (including specific training course and awareness materials), and security planning."}], "metadata": {"source": "Computer Security Division 2009 Annual Report", "cmmc_level": "2", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Computer Security Division 2012 Annual Report:\n\ndf00)ing and International Trade Center in Washington, D.C. The conference offered important sessions that focused on broad topics of interest to the healthcare and health IT security community.\nOver 500 attendees from federal, state, and local governments, academia, HIPAA-covereGLYPH(cmap:df00) entities anGLYPH(cmap:df00) business associates, industry groups, and vendors heard from, and interacteGLYPH(cmap:df00) with, healthcare, security, anGLYPH(cmap:df00) privacy experts on technologies and methodologies for safeguarding health information and for implementing the requirements of the HIPAA Security Rule. Presentations covered a variety of current topics including updates on OCR's health information privacy and security audit and enforcement activities; establishing an access audit program; securing mobile devices; securing health information in the Cloud;"}], "metadata": {"source": "Computer Security Division 2012 Annual Report", "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 AC.L2-3.1.8 (NIST 3.1.8)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.1.8. 3.1.8."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "nist_control": "3.1.8", "cmmc_practice_id": "AC.L2-3.1.8", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The NIST Cybersecurity Framework (CSF) 2.0 provide? (Part 5)"}, {"role": "assistant", "content": "pecific outcomes. Suggestions for how specific outcomes may be achieved are provided in an expanding suite of online resources that complement the CSF, including a series of Quick Start Guides (QSGs).\nAlso, various tools offer downloadable formats to help organizations that choose to automate some of their processes. The QSGs suggest initial ways to use the CSF and invite the reader to explore the CSF and related resources in greater depth. Available through the NIST CSF website, the CSF and these supplementary resources from NIST and others should be viewed as a 'CSF portfolio' to help manage and reduce risks. Regardless of how it is applied, the CSF prompts its users to consider their cybersecurity posture in context and then adapt the CSF to their specific needs. Building on previous versions, CSF 2.0 contains new features that highlight the importance of governance and supply chains . Special attention is paid to the QSGs to ensure that the CSF is relevant and readily accessible by smaller organizations as well as their larger counterparts. NIST now provides Implementation Examples and Informative References , which are available online and updated regularly. Creating current and target state Organizational Profiles helps organizations to compare where they are versus where they want or need to be and allows them to implement and assess security controls more quickly. Cybersecurity risks are expanding constantly, and managing those risks must be a continuous process. This is true regardless of whether an organization is just beginning to confront its cybersecurity challenges or whether it has been active for many years with a sophisticated, well-resourced cybersecurity team. The CSF is designed to be valuable for any type of organization and is expected to provide appropriate guidance over a long time. ## 1. Cybersecurity Framework (CSF) Overview\n\nThis document is version 2.0 of the NIST Cybersecurity Framework ( Framework or CSF )."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Introduction to Cybersecurity for Commercial Satellite Operations:\n\n| Functions | Subcategories | Informative | Reference |\n|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------|-------------------------------------------------|\n| | | SP 800-53, Rev. 4 | SP 800-53, Rev. 5 |\n| | PR.DS-6: Integrity-checking mechanisms are used to verify software, firmware, and information integrity. | SI-7 | SI-7, SI-10 |\n| | PR.DS-8: Integrity-checking mechanisms are used to verify hardware integrity. | SI-7 | SI-7 |\n| | PR.IP-1: A baseline configuration of information technology/industrial control systems that incorporates security principles (e.g., concept of least functionality) is created and maintained. | CM-2, CM-3, CM-4, CM-5, CM-6, CM-7, CM-9, SA-10 | CM-2, CM-3, CM-4, CM-5, CM-6, CM-7, CM-9, SA-10 |\n| | PR.IP-3: Configuration change control processes are in place."}], "metadata": {"source": "Introduction to Cybersecurity for Commercial Satellite Operations", "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 Incident Response?"}, {"role": "assistant", "content": "According to Threat Assessment of Malicious Code and External Attacks:\n\ntributed Intrusion Detection System) -motivation, architecture, and an early prototype. In Proceedings of the lfth National Computer Security Conference , 1991. - [SH82] John F. Shoch and Jon A. Hupp.\nThe 'worm' programs -early experience with a distributed computation. Association for Computing Machinery , 25(3), March 1982. - [Spa89] Eugene Spafford. The internet worm program: An analysis. Computer Communication Review , 19(1), January 1989. - [Wac91] John Wack. Establishing a Computer Security Incident Response Capability (CSIRC). NIST Special Publication 800-3, National Institute of Standards and Technology, 1991."}], "metadata": {"source": "Threat Assessment of Malicious Code and External Attacks", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Federal S_MIME V3 Client Profile:\n\n| Cryptographic Algorithm Suite Conformance........................................................\n| 3 |\n| 2.1.2 | PKI Profile Conformance ....................................................................................... | 4 |\n| 2.1.3 | Cryptographic Messaging Systems (CMS) Content Types .................................... | 5 |\n| 2.1.4 | MIME Encoding | ..................................................................................................... 5 |\n| 2.1.5 | Mail Access Protocols (POP/IMAP) | ......................................................................"}], "metadata": {"source": "Federal S_MIME V3 Client Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.7 (NIST 3.6.7)?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\n3.6.7 | This specifies that the public key MAY be used to verify signatures on CHUIDs and biometric data records."}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "cmmc_level": "2", "nist_control": "3.6.7", "cmmc_practice_id": "IR.L2-3.6.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Computer Security Division 2004 Annual Report:\n\n- Standards to be used by Federal agencies to categorize information and information systems based on the objectives of providing appropriate levels of information security according to a range of risk levels Developed Special Publication (SP) 800-37, Guidelines for the Security Certification and Accreditation of Federal Information Technology Systems (final version issued May 2004) - Guidelines recommending the types of information and information systems to be included in each category Developed and issued FIPS 199, Standards for Security Categorization of Federal Information and Information Systems (final version issued February 2004) - Minimum information security requirements (management, operational and technical security controls) for information and information systems in each such category Developed SP 800-53, Security Controls for Federal Information Systems (first public draft issued October 2003), and continued work on SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems (first public draft to be issued January 2005) - Incident detection and handling guidelines Developed SP 800-61, Computer Security Incident Handling Guide (final version issued January 2004) - Provide assistance to agencies and private sector Conduct ongoing, substantial reimbursable and non-reimbursable assistance support, including many outreach efforts such as the Federal Information Systems Security Educators' Association (FISSEA), the Federal"}], "metadata": {"source": "Computer Security Division 2004 Annual Report", "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 Metrics and Methodology for Hardware Security Constructs:\n\n| ID | Description |\n|------|----------------------------------------|\n| 26 | Leveraging Race Conditions |\n| 113 | Interface Manipulation |\n| 114 | Authentication Abuse |\n| 122 | Privilege Abuse |\n| 124 | Shared Resource Manipulation |\n| 176 | Configuration/Environment Manipulation |\n| 188 | Reverse Engineering |\n| 192 | Protocol Analysis |\n| 233 | Privilege Escalation |\n| 441 | Malicious Logic Insertion |\n| 624 | Hardware Fault Injection |"}], "metadata": {"source": "Metrics and Methodology for Hardware Security Constructs", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Getting Ready for Post-Quantum Cryptography_ Exploring Challenges Associated with Adopting and Using Post-Quantum Cryptographic Algorithms:\n\n...6 |\n\nstandards is completed. Unfortunately, the implementation of post-quantum public-key standards is likely to be more problematic than the introduction of new classical cryptographic algorithms.\nIn the absence of significant implementation planning, it may be decades before the community replaces most of the vulnerable public-key systems currently in use."}], "metadata": {"source": "Getting Ready for Post-Quantum Cryptography_ Exploring Challenges Associated with Adopting and Using Post-Quantum Cryptographic Algorithms", "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.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Standard Security Label for GOSIP_ an Invitational Workshop:\n\n3.3.5 Security Tag Type 4 | 4. 3.3.5 Security Tag Type 4 | 4. 3.3.5 Security Tag Type 4 | 4."}], "metadata": {"source": "Standard Security Label for GOSIP_ an Invitational Workshop", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\n3.2.3\n\nU. 3.2.3\n\nIdentity-Based Encryption\n\nKey distribution and key revocation are some of the most fundamental problems in key\ndistribution for systems."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic:\n\n| Company Overview.................................................................................................................2 |\n|--------------------------------------------------------------------------------------------------------------------------------------------|\n| Risk Profile ..........................................................................................................................2 |\n| Highlighted Practices in Cyber Supply Chain Management ..................................................2 |\n| Organizational Approach to Supply Chain Risk and Cybersecurity............................................3 |\n| Supplier Management.............................................................................................................3 |\n| Key Aspects of Managing Supplier Relationships .................................................................3 |\n| Measuring Supplier Risk ......................................................................................................4 |\n| Quality Management and Continuous Improvement...........................................................4 |\n| Incident Response and Recovery .........................................................................................4 |\n| Lessons Learned and Improvement Opportunities ..................................................................5 |\n| References ..............................................................................................................................5 |\n\n## Incident Response and Recovery\n\nThe key focus of the Mayo Clinic's cybersecurity and supply chain incident response plans is the continuation of patient care."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Managing Information Security Risk_ Organization, Mission, and Information System View:\n\nzations. The risk management activities at Tier 2 begin with the identification and establishment of riskaware mission/business processes to support the organizational missions and business functions.\nA risk-aware mission/business process is one that explicitly takes into account the likely risk such a process would cause if implemented. Risk aware processes are designed to manage risk in accordance with the risk management strategy defined at Tier 1 and explicitly account for risk when evaluating the mission/business activities and decisions at Tier 2. 34 Implementing riskaware mission/business processes requires a thorough understanding of the organizational missions and business functions and the relationships among missions/business functions and supporting processes. This understanding is a prerequisite to building mission/business processes sufficiently resilient to withstand a wide variety of threats including routine and sophisticated cyber attacks, errors/accidents, and natural disasters. An important part of achieving risk-aware processes is the understanding of senior leaders/executives of: (i) the types of threat sources and threat events that can adversely affect the ability of organizations to successfully execute their missions/business functions); (ii) the potential adverse impacts/consequences on organizational operations and assets, individuals, other organizations, or the Nation if the confidentiality, integrity, or availability of information or information systems used in a mission/business process is compromised; and (iii) the likely resilience to such a compromise that can be achieved with a given mission/business process definition, applying realistic expectations for the resilience of information technology."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case:\n\n- Machining Stations 1, 2, 3 - All manufacturing functions are performed by sequential CNC machining stations (1, 2, and 3). Each station uses preprogrammed operations (e.g., G code) to complete its required manufacturing process tasks. This code, and all station functions, have direct control over the output product quality. - Inspection Station 4 - If product quality has been impacted (i.e., the product dimensions do not meet the defined specifications), the inspection station will reject the part. Misconfiguration or modification of specifications loaded into the inspection station could allow out-of-spec parts to erroneously pass inspection. - Robots - Tending of parts between the machines is handled by the two workcell robots. This process requires accurate and repeatable placement of parts within the machining station fixtures, which is performed through proper robot calibration and the programming of waypoint coordinates. Parts that are not properly placed within fixtures, or collide with the fixtures, may not meet product quality specifications. - Supervisory PLC - The supervisory PLC tracks each part as it goes through the manufacturing process and commands the robots to transport each part between machines in a sequential manner. If a robot executes a job out-of-order, a part may bypass one of the machining stations, impacting product quality, or damaging one of the downstream stations. - Human Machine Interface (HMI) - Operators can manipulate workcell parameters, machining station programs, and inspection station acceptance parameters through the HMI. Modification of any of these parameters outside of expected bounds can impact product quality. - Engineering Workstation - Privileged control and administrative functions are granted to authorized personnel via the Engineering Workstation."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Automation Support for Control Assessments_ Project Update and Vision:\n\nIn 2017, the National Institute of Standards and Technology (NIST) published a methodology for supporting the automation of Special Publication (SP) 800-53 control assessments in the form of Interagency Report (IR) 8011. IR 8011 is a multi-volume series that starts with an overview of the methodology (volume 1) and provides guidance and specifications for automating the assessment of controls that support specific information security continuous monitoring security capabilities, one volume per capability. Four volumes have been released so far, and more volumes are in development. In 2023, the NIST Risk Management Framework project responsible for the development and maintenance of Federal Information Security Modernization Act (FISMA)-supporting technical publications and the IR 8011 series performed an internal review of the IR 8011 project. This review yielded results that offered the IR 8011 Development Team opportunities to improve the current IR 8011 methodology, facilitate its adoption, and more. This cybersecurity white paper summarizes some of the findings from this internal review. | 1. Introduction...................................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Updates to the IR 8011 Methodology..............................................................................................2 |\n| 3. Updated Guidance and Updated Language......................................................................................6 |\n| 4. Interested Party Engagement .........................................................................................................7 |\n| 5."}], "metadata": {"source": "Automation Support for Control Assessments_ Project Update and Vision", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\nImpact Levels .......................................................... 76\nImpact Levels for the CI&A Categories ......................................................................................\n77\n3.3\n3.4 Selection of Security Requirements ............................................................................................. 79\n3.5 Security Requirements Example .................................................................................................. 80\n3.6 Recommended Security Requirements ........................................................................................ 81\n3.7 Access Control (SG.AC) ............................................................................................................. 93\n3.8 Awareness and Training (SG.AT) ............................................................................................. 107\n3.9 Audit and Accountability (SG.AU) ........................................................................................... 111\n3.10 Security Assessment and Authorization (SG.CA) ..................................................................... 120\n3.11 Configuration Management (SG.CM) ....................................................................................... 124\n3.12 Continuity of Operations (SG.CP) ............................................................................................. 132\n3.13 Identification and Authentication (SG.IA) ................................................................................ 139\n3.14 Information and Document Management (SG.ID) .................................................................... 142\n3.15 Incident Response (SG.IR) ........................................................................................................ 146\n3.16 Smart Grid Information System Development and Maintenance (SG.MA) .............................."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "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 Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective provide? (Part 3)"}, {"role": "assistant", "content": "Engagement in International Standardization to Achieve U.S. Objectives for Cybersecurity . It provides a current summary of ongoing activities in critical international cybersecurity standardization.\nIt also provides information for Federal agencies and other stakeholders to help plan more effective participation in international cybersecurity standards development and related conformity assessment activities. ## Table of Contents\n\n| Introduction ........................................................................................................................................1 | Introduction ........................................................................................................................................1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1 | Why are cybersecurity standards critical? .................................................................................2 |\n| 2 | Why is conformity assessment for cybersecurity standards important?"}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guidelines for the Secure Deployment of IPv6:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | 1 |\n|--------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|\n| | Introduction ................................................................................................................... | Introduction ..................................................................................................................."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.3 (NIST 3.6.3)?"}, {"role": "assistant", "content": "According to Integrating Cybersecurity and Enterprise Risk Management (ERM):\n\n3.6.3 | Continuous Improvement ... 3.6.3 Continuous Improvement\n\nA risk-aware culture should be looking for opportunities for improvement-reinforcing effective practices and adjusting to correct deficiencies."}], "metadata": {"source": "Integrating Cybersecurity and Enterprise Risk Management (ERM)", "cmmc_level": "all", "nist_control": "3.6.3", "cmmc_practice_id": "IR.L2-3.6.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 Guide to Computer Security Log Management:\n\nretrieved Web pages to make additional accesses to those pages more efficient. Web proxies can also be used to restrict Web access and to add a layer of protection between Web clients and Web servers.\nWeb proxies often keep a record of all URLs accessed through them. - GLYPH<c=31,font=/APONEK+Webdings> Vulnerability Management Software. Vulnerability management software, which includes patch management software and vulnerability assessment software, typically logs the patch installation history and vulnerability status of each host, which includes known vulnerabilities and missing software updates. 5 Vulnerability management software may also record additional information about hosts' configurations. Vulnerability management software typically runs occasionally, not continuously, and is likely to generate large batches of log entries. - GLYPH<c=31,font=/APONEK+Webdings> Authentication Servers. Authentication servers, including directory servers and single sign-on servers, typically log each authentication attempt, including its origin, username, success or failure, and date and time."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Guide to Information Technology Security Services:\n\n3.2.6 Review IT Security\n\nThe Contractor shall examine sensitive and critical IT systems and data files."}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Practical Combinatorial Testing:\n\n| 1 INTRODUCTION .........................................................................................2 | 1 INTRODUCTION .........................................................................................2 | 1 INTRODUCTION .........................................................................................2 | | |-------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------| | 1.1 | 1.1 | Authority..............................................................................................................2 | | | 1.2 | 1.2 | Document Scope and Purpose | .............................................................................2 | | 1.3 | 1.3 | Audience and Assumptions..................................................................................3 | | | 1.4 | 1.4 | Organization: How to use this Document...........................................................3 | | | 2 COMBINATORIAL METHODSIN TESTING.................................................4 | 2 COMBINATORIAL METHODSIN TESTING.................................................4 | 2 COMBINATORIAL METHODSIN TESTING.................................................4 | | | 2.1 | 2.1 | Two Forms of Combinatorial Testing..................................................................6 | | | 2.2 | 2.2 | The Test Oracle Problem | .....................................................................................9 | | 2.3 | 2.3 | Chapter Summary | ..............................................................................................10 | | 3 | CONFIGURATION TESTING ...................................................................."}], "metadata": {"source": "Practical Combinatorial Testing", "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 Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight:\n\nlace of management experience and prudent judgement. Aggregating the risk analysis from multiple CSRRs follows the same approach as that described in NISTIR 8286A, Section 2.3, Detailed Risk Analysis.\nThe method will vary by enterprise, but, for example, a three-point estimation could be used to complete the likelihood and impact columns on the combined register. Using the lowest observed value as the best case, the highest value as the worst case, and the mean value of the others as the most likely, the business unit risk manager could calculate these values. That manager could also apply their knowledge of the personnel and processes used to generate the CSRRs (e.g., a particularly detailed estimate might influence the understanding of the most likely value)."}], "metadata": {"source": "Staging Cybersecurity Risks for Enterprise Risk Management and Governance Oversight", "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 Access Control?"}, {"role": "assistant", "content": "According to Foundational Cybersecurity Activities for IoT Device Manufacturers:\n\n5. What will the nature of the IoT device's data be? There is a great deal of variability in data stored by IoT devices; some devices do not store any data, while others store data that could cause significant harm if accessed or modified by unauthorized entities. Understanding the nature of expected data on a device in the context of the customers and use cases can help manufacturers identify which device cybersecurity capabilities may be needed for protecting device data, such as data encryption, device and user authentication, data validation, access control, and backup/restore. 6. What is the degree of trust in the IoT device that customers may need? Customers may expect certain device cybersecurity capabilities and implementations that allow for specific assurances about the cybersecurity of the device and/or data. For example, in some contexts, additional trust that data is protected could be achieved by adding protection of data in use within the device. This would go beyond the usual goals of data protection (e.g., protecting data at rest and in transit). 7. What complexities will be introduced by the IoT device interacting with other devices, systems, and environments? For example, complexity can be driven by new uses of IoT and IoT devices, new combinations of those devices with each other and conventional IT devices, and increasing interconnections among devices and systems. These complexities could mean new functionality, which may have human-safety or privacy implications, that will be connected via networking technologies to systems that do not appropriately mitigate these risks. An IoT device that can stream images from inside the home, such as a smart baby monitor, or that can alter the environment to the point of danger, such as a smart oven, might require safeguards not usually considered for conventional IT devices. IoT can also introduce complexities related to scale, which could make ongoing management and support of devices difficult."}], "metadata": {"source": "Foundational Cybersecurity Activities for IoT Device Manufacturers", "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 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Small Business Information Security_ The Fundamentals:\n\n| FOREWORD | ....................................................................................................................................................... PURPOSE ........................................................................................................................................................... | ....................................................................................................................................................... PURPOSE ........................................................................................................................................................... | 1 1 |\n|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|\n| 1 | BACKGROUND: WHAT IS INFORMATION SECURITY AND CYBERSECURITY?.............................................. | BACKGROUND: WHAT IS INFORMATION SECURITY AND CYBERSECURITY?.............................................. | 2 |\n| | 1.1 | WHY SMALL BUSINESSES?"}], "metadata": {"source": "Small Business Information Security_ The Fundamentals", "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 A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems:\n\n- Uniform Resource Identifier (URI) to identify terminology and protocols that allow parties to read the DID document\n- DID that identifies the subject of the DID document\n- Set of public keys used for authentication, authorization, and communication mechanisms\n- Set of authentication methods used for the DID subject to prove ownership of the DID to another entity\n- Set of authorization and delegation methods for the DID subject to allow another entity to operate on their behalf (i.e., custodians)\n- Set of service endpoints to describe where and how to interact with the DID subject\n- Timestamp for when the document was created [optional]\n- Timestamp for when the document was last updated [optional]\n- Cryptographic proof of integrity (e.g., digital signature) [optional]\n\nA blockchain is used to support the mapping of keys to identifiers by acting as an integrityprotected 'bulletin board' for public key infrastructure (PKI). 1 Blockchains may be applicationspecific, such as Hyperledger Indy [24], and/or may support native smart contract platforms. In most cases, this 'bulletin board' for PKI-sometimes augmented by separate protocols atop the blockchain-forms an identifier management system (called DID method if it follows the DID specification). In addition to keys and identifiers, credentials may also rely on the blockchain.\n\nOnchain credentials often only require onchain storage for the hashes of the credentials with the non-hash data being stored on any data store a subject has access to, be it a designated custodian or a decentralized storage system such as IPFS [40]. 6 The integrity of the data may be checked by the receiving party by hashing the credential and comparing the hash with the one found on the blockchain. The hashes are often stored as state variables or blockchain logs, the latter being sometimes cheaper than onchain storage (e.g., Ethereum events)."}], "metadata": {"source": "A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Security Labels for Open Systems_ an Invitational Workshop:\n\nple Label-Set Associations | 14 |\n| 9.1 Support by variable- and multi- set-labelling facilities | 14 |\n| 9.2 Support by single-labelling facilities | 14 |\n| 10.\nImplementation Choices and Rationale | 16 |\n| References | 17 |"}], "metadata": {"source": "Security Labels for Open Systems_ an Invitational Workshop", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\nSecurity awareness programs aim to assist employees in recognizing and responding to security issues with a goal of achieving long-term behavior changes. Security awareness professionals are individuals who are tasked with managing and executing the security awareness programs within their organizations. Prior industry surveys and research studies have identified challenges security awareness professionals face. Many members of security awareness teams perform security awareness duties on a part-time basis without a job title that reflects their duties, and they may lack sufficient professional skills (e.g., communications, relationship-building) that were viewed as essential in security awareness roles. In addition, the lack of understanding that security awareness is a unique discipline may lead to ill-prepared awareness professionals. However, it is unclear if these challenges also apply to security awareness professionals in the United States (U.S.) government. other fields, including non-IT fields such as instructional design and education, communications, and human resources. We found that 40% of participants had only ever worked in a technical field (cybersecurity, IT, or software development). Cybersecurity awareness (hereafter shortened to 'security awareness') programs aim to help employees recognize and appropriately respond to security issues, with a goal of achieving longterm behavior change [WILSON]. Security awareness professionals are individuals who are tasked with managing and executing the security awareness programs within their organizations. Prior industry surveys and research studies have identified challenges security awareness professionals face. Many professionals perform security awareness duties on a part-time basis without a job title that reflects their duties, and they may lack sufficient professional skills (e.g., communications, relationship-building) that are viewed as essential in security awareness roles [SANS][WOELK]."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to 2016 NIST_ITL Cybersecurity Program Annual Report:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "2016 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N:\n\n| 1.2 Audience.........................................................................................................\n| 1 |\n| 1.3 | Document Structure........................................................................................ | 1 |\n| 2 | Background............................................................................................................2 | Background............................................................................................................2 |\n| 2.1 | XACML ........................................................................................................... | 4 |\n| 2.2 | NGAC | ............................................................................................................."}], "metadata": {"source": "A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N", "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 Incident Response?"}, {"role": "assistant", "content": "According to Security of Interactive and Automated Access Management Using Secure Shell (SSH):\n\nStolen, leaked, derived, and unterminated identity keys pose a similar problem to stolen, leaked, derived, and unterminated interactive user account credentials. Anyone who may have obtained a copy of an identity key-by copying it from a host, by accessing a backup, by having malware harvest keys, by performing factoring to derive a key, etc.-may use that key to attempt to gain unauthorized access to a user account on one or more servers in the organization. Once access to a user account has been gained, it is generally possible to access and modify any data for that user account-including reading and modifying the memory of processes running under that user account, and modifying any executable programs owned by that user account.\n\nMalware can be engineered to use SSH keys to spread when automated access is allowed. The mesh of interactive and automated access relationships is so dense in many cases that it is likely that an attack can spread (pivot) to most servers in an organization after penetrating the first few servers, especially if other attack vectors are used to escalate privileges. See Figure 4-1 for an illustration of pivoting.\n\nThe purpose of continuous monitoring is to ensure that the processes for provisioning, life cycle management, and termination are followed and enforced. It is also important for detecting unauthorized access that may have been illicitly provisioned by attackers as a backdoor into systems. Unauthorized and misconfigured SSH user keys should be detected. For example, anyone or anything (including malware) with access to a superuser account can technically configure new authenticators granting access to any account."}], "metadata": {"source": "Security of Interactive and Automated Access Management Using Secure Shell (SSH)", "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 Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program provide? (Part 3)"}, {"role": "assistant", "content": "ght, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-11-04 Supersedes NIST SP 800-55 Rev.\n1 (July 2008) https://doi.org/10.6028/NIST.SP.800-55r1\n\n## How to Cite this NIST Technical Series Publication\n\nSchroeder K, Trinh H, Pillitteri VY (2024) Measurement Guide for Information Security: Volume 2 - Developing an Information Security Measurement Program. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-55v2. https://doi.org/10.6028/NIST.SP.800-55v2\n\n## Author ORCID iDs\n\nKatherine Schroeder: 0000-0002-4129-9243 Hung Trinh: 0000-0002-3323-0836 Victoria Yan Pillitteri: 0000-0002-7446-7506\n\n## Contact Information\n\ncyber-measures@list.nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/55/v2/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis document provides guidance on how an organization can develop an information security measurement program with a flexible structure for approaching activities around the development and implementation of information security measures. ## Keywords\n\nassessment; information security; measurement; measures; metrics; performance; program; reports; security controls. ## 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": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Secure Domain Name System (DNS) Deployment Guide:\n\nThe Domain Name System (DNS) is a distributed computing system that enables access to Internet resources by user-friendly domain names rather than IP addresses, by translating domain names to IP addresses and back. The DNS infrastructure is made up of computing and communication entities called Name Servers each of which contains information about a small portion of the domain name space. The domain name data provided by DNS is intended to be available to any computer located anywhere in the Internet.This document provides deployment guidelines for securing DNS within an enterprise. Because DNS data is meant to be public, preserving the confidentiality of DNS data. The primary security goals for DNS are data integrity and source authentication, which are needed to ensure the authenticity of domain name information and maintain the integrity of domain name information in transit. This document provides extensive guidance on maintaining data integrity and performing source authentication. DNS components are often subjected to denial-of-service attacks intended to disrupt access to the resources whose domain names are handled by the attacked DNS components. This document presents guidelines for configuring DNS deployments to prevent many denial-of-service attacks that exploit vulnerabilities in various DNS components. This document provides deployment guidelines for securing DNS within an enterprise. Because DNS data is meant to be public, preserving the confidentiality of DNS data pertaining to publicly accessible IT resources is not a concern. The primary security goals for DNS are data integrity and source authentication, which are needed to ensure the authenticity of domain name information and maintain the integrity of domain name information in transit. This document provides extensive guidance on maintaining data integrity and performing source authentication."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment Guide", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations:\n\nOrganizations shall select cryptographic devices and applications with cryptographic functions, 58 key management products 59 and key management services 60 that conform to NIST standards to the maximum extent possible, and new cryptographic application development efforts shall comply with NIST key management recommendations. Accordingly, NIST criteria for the security, accuracy, and utility of key management products in electronic and physical forms shall be met (e.g., see FIPS 140, SP 800-53, and Part 1). The methods used in the design, evaluation, programming, generation, production, establishment, quality assurance, and inspection procedures for key management products and services should be structured to satisfy such criteria. | The following publications are provided for reference. The provided publication dates refer to last available version of the document as of the publication of this revision of SP 800-57 Part When later revisions of these referenced documents are available, those versions should referenced instead. | The following publications are provided for reference. The provided publication dates refer to last available version of the document as of the publication of this revision of SP 800-57 Part When later revisions of these referenced documents are available, those versions should referenced instead."}], "metadata": {"source": "Recommendation for Key Management_ Part 2 – Best Practices for Key Management 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body ...................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to A Security Perspective on the Web3 Paradigm:\n\nblockchain; cryptocurrency; data; decentralized; decentralized identity; non-fungible tokens; smart contracts; tokens; Web3. | 1. Introduction...................................................................................................................................1 |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Background....................................................................................................................................2 |\n| 3. Web3 Overview .............................................................................................................................5 |\n| 3.3.1. Existing Internet Technologies .....................................................................................................8 |\n| 3.3.2. Mobile Technology.......................................................................................................................8 |\n| 3.3.3. Digital Identity and Verifiable Credentials ...................................................................................9 |\n| 3.3.4. Decentralized Systems and Smart Contracts ...............................................................................9 |\n| 4. Web3 Security and Privacy ...........................................................................................................12 |\n| 5. Conclusion ...................................................................................................................................21 |\n| References.......................................................................................................................................22 |\n| List of Tables |\n| Table 2."}], "metadata": {"source": "A Security Perspective on the Web3 Paradigm", "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 Usability and Security Considerations for Public Safety Mobile Authentication:\n\nfirst responders from EMS or Law Enforcement if they are not wearing masks or protective eyewear. Speaker recognition will be difficult due to the noisy environments in which first responders operate.\nKeystroke dynamics authentication has the same critical usability issues described above for the other text entry methods (e.g., KBA, passwords, PINs). - Our analysis concludes that there are three authentication methods that are currently more promising for first responders because they do not pose critical or significant usability issues. They are embedded cryptographic tokens, on-body detection, and location-based awareness. Depending upon the implementation, these methods should not require additional user interaction to authenticate with the mobile device when it is already unlocked. For example, embedded cryptographic tokens should be configured such that it does not require a user to select between multiple digital certificates. If first responders are sharing devices, it may be necessary for multiple user profiles to be enabled on the same device, to allow the correct certificates to be used for a given responder."}], "metadata": {"source": "Usability and Security Considerations for Public Safety Mobile Authentication", "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 Program Review for Information Security Management Assistance (PRISMA):\n\n- Tests are routinely conducted to evaluate the adequacy and effectiveness of all implementations,\n- Tests ensure that all policies, procedures, and controls are acting as intended and that they ensure the appropriate information security level,\n- Effective corrective actions are taken to address identified weaknesses, including those identified as a result of potential or actual information security incidents or through information security alerts issued by US-CERT, vendors, and other trusted sources,\n- Self-assessments, a type of test that can be performed by agency staff, by contractors, or others engaged by agency management, are routinely conducted to evaluate the adequacy and effectiveness of all implementations,\n- Independent audits such as those arranged by the Government Accountability Office (GAO) or an agency Inspector General (IG), are an important check on agency performance, but are not to be viewed as a substitute for evaluations initiated by agency management,\n- Information gleaned from records of potential and actual Information security incidents and from security alerts, such as those issued by software vendors are considered as test results. Such information can identify specific vulnerabilities and provide insights into the latest threats and resulting risk,\n- Evaluation requirements, including requirements regarding the type and frequency of testing, are documented, approved, and effectively implemented, and\n- The frequency and rigor with which individual controls are tested depend on the risks that will be posed if the controls are not operating effectively."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "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 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 Access Control?"}, {"role": "assistant", "content": "According to Secure Domain Name System (DNS) Deployment Guide:\n\n| 13-21 | | 13.2 Establishing Initial Trust Anchors........................................................................13-22 | | | 13.3 Maintaining Trust Anchors..................................................................................13-23 | | | 13.4 Recommendations Summary | .............................................................................13-24 | | List of Appendices | List of Appendices | | Appendix A- Definitions of Important Terms....................................................................A-1 | | | Appendix B-Vendor Specific Steps to Meet Checklist Items..........................................B-1 | | | AppendixC- Acronyms......................................................................................................C-1 | | | Appendix D-Bibliography..................................................................................................D-1 | | | List of Figures | List of Figures | | Figure 2-1."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment Guide", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## Analyzing Collusion Threats in the Semiconductor Supply Chain\n\nRekhi S, Amberiadis K, Akib AA, Srivastava A (2025) Analyzing Collusion Threats in the Semiconductor Supply Chain. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 46. https://doi.org/10.6028/NIST.CSWP.46\n\nThis work proposes a framework for analyzing threats related to the semiconductor supply chain. The framework introduces a metric that quantifies the severity of different threats subjected to a collusion of adversaries from different stages of the supply chain. Two different case studies are provided to describe the real-life application of the framework. The metrics and analysis aim to guide security efforts and optimize the trade-offs of hardware security and costs."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to A Formal Description of the SDNS Security Protocol at Layer 4 (SP4):\n\n3.3.1 | NA | NA | 1,5 |\n| final s/n | 6. 3.3.1 | NA | NA | 1,5 |\n| connection release | 6."}], "metadata": {"source": "A Formal Description of the SDNS Security Protocol at Layer 4 (SP4)", "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 Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance:\n\n- Improved productivity: DHS Customs and Border Patrol (CBP) used IoT to process vehicles faster at ports of entry, improving their ability to identify threats and take action.\n\nMr. Fagan then presented the RMF perspective positioning an IoT device as a system element in a federal information system and described the need to take a system view to fully grasp an IoT device's potential impact on system risk. He explained that introducing an IoT device or adding an Internet connection to support a device's operations may bring new mission or safety risks that in turn require additional security controls (e.g., if an IoT device is deployed in place of an operational technology [OT] device that wasn't Internet-connected). He highlighted various aspects of IoT device implementation (e.g., processing capability, power limitations, connectivity patterns) that can influence the device's impact on the system's security risks. He then walked through the steps of a risk assessment, as defined in the RMF, and some associated IoT device considerations that can apply at each step of the process.\n\n- NIST should consider utilizing the Cybersecurity Framework (CSF) when describing risk associated with IoT devices.\n- Enterprises, especially larger enterprises, are more familiar with making conscious riskbased assessments; risk evaluation may be implicit in consumer decision making, but risk language may not capture key concerns of consumers.\n- For consumers, consider focusing on the privacy implications of IoT devices which could be more useful for consumers.\n- A pilot effort applying the descriptors could be very useful in helping to refine them.\n- The viewpoint of the party doing the risk assessment may have a significant influence on their view of the risk of a product (e.g., assessment in a laboratory vs. an operational context)"}], "metadata": {"source": "Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance", "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 Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements:\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\n3 The SCAP Validation Program does not provide physical certificates to the participating vendors.\n\nSCAP.V.100.1: The vendor SHALL indicate where in the product documentation information regarding the use of SCAP and its components can be found. This MAY be a physical document or an electronic document (e.g., a PDF, help file, etc.)."}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.3 Validation Program Test Requirements", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Random Bit Generator (RBG) Constructions:\n\nCryptography and security applications make extensive use of random bits. However, the generation of random bits is challenging in many practical applications of cryptography. The National Institute of Standards and Technology (NIST) developed the Special Publication (SP) 80090 series to support the generation of high-quality random bits for both cryptographic and noncryptographic purposes. The SP 800-90 series consists of three parts:\n\n| [AIS20] | BSI (2025) Anwendungshinweise und Interpretationen zum Schema (AIS) (AIS 20, Version 4) (Bundesamt für Sicherheit in der Informationstechnik [BSI], Bonn, Germany). Available at https://www.bsi.bund.de/dok/ais-20- |\n|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [AIS31] | BSI (2025) Funktionalitätsklassen und Evaluationsmethodologie für physikalische Zufallszahlengeneratoren (AIS 31, Version 4) (Bundesamt für Sicherheit in der Informationstechnik [BSI], Bonn, Germany). Available at |\n| [BSIFunc] | https://www.bsi.bund.de/dok/ais-20-31 Peter M, Schindler W(2024) A Proposal for Functionality Classes for Random Number Generators (Version 3.0). (Bundesamt für Sicherheit in der Informationstechnik [BSI], Bonn, Germany). Available at https://www.bsi.bund.de/dok/ais-20-31-appx-2024 |\n| [FIPS_140] | National Institute of Standards and Technology (2019) Security Requirements for Cryptographic Modules. (Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) NIST FIPS 140-3."}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "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 Proceedings of the Workshop of the Federal Criteria for Information Technology Security:\n\nIntegrity 18\n\nIntegrity 19\n\n- The unbundling of functional requirements from each other and from assurances.\n- The creation of protection profiles by assembling pre-defined components and elaborating them to specific product targets.\n- The explicit sq)aration of documentation, process, and evaluation assurance.\n- Recognition ofEase of Use, Physical Protection, and Flaw Remediation (this > thought to be especially important to retain) as requirements."}], "metadata": {"source": "Proceedings of the Workshop of the Federal Criteria for Information Technology Security", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Managing the Security of Information Exchanges:\n\nThe less expensive alternative is to connect systems over a public network (e.g., the internet) using a VPN. A VPN is a network that enables two or more parties to communicate securely across a public network by creating a private connection, or 'tunnel,' between endpoints. Information transmitted via VPN over a public network can be intercepted by unauthorized parties. However, the use of authentication and encryption helps ensure the confidentiality and integrity of the information\n\n- Network Interconnection - A physical or virtual communications link between two or more networks operated by different organizations or operated within the same organization but within different authorization boundaries. - Application Interconnection - A logical communications link between two or more applications operated by different organizations or within the same organization but within different authorization boundaries used to exchange information or provide information services (e.g., authentication, logging). Application interconnections include file-sharing services or applications and information exchange feeds that occur at the session, presentation, or application layer. - future growth is anticipated. If new hardware is required, select products that are interoperable with existing hardware. - Specific Software Requirements : Identify software needed to support the information exchange, including software for information exchange management and file sharing services, and on what hardware the software is to be installed (e.g., firewalls, servers, workstations, and laptops). Determine whether existing software is sufficient or whether additional software is required. If new software is required, select products that are interoperable with existing software. - User Community : Define the community of users requiring access to the exchanged information."}], "metadata": {"source": "Managing the Security of Information Exchanges", "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 COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0 provide? (Part 5)"}, {"role": "assistant", "content": "INTRODUCTION.............................................................................................................................. | 1. INTRODUCTION.............................................................................................................................. | 1 |\n| 1.1 | I DENTIFICATION...........................................................................................................................1 | |\n| 1.2 | OVERVIEW....................................................................................................................................1 | |\n| 2. TOE DESCRIPTION......................................................................................................................... | 2. TOE DESCRIPTION........................................................................................................................."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions:\n\n3.1.3 | Converting State Arrays to Strings... 3.1.3 Converting State Arrays to Strings\n\nLet A denote a state array. 3.1.3."}], "metadata": {"source": "SHA-3 Standard_ Permutation-Based Hash and Extendable-Output Functions", "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 guidance does Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations provide?"}, {"role": "assistant", "content": "## Summary of NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations\n\nKelley Dempsey Computer Security Division Information Technology Laboratory\n\nGreg Witte Doug Rike G2, Inc. Annapolis Junction, MD\n\nFebruary 19, 2014\n\n\n\n## Abstract\n\nThis white paper provides an overview of NIST Special Publication (SP) 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations , which was published April 30, 2013. ## Keywords\n\nassurance; computer security; FIPS Publication 199; FIPS Publication 200, FISMA; Privacy Act; Risk Management Framework; security controls; security requirements\n\n## Disclaimer\n\nAny mention of commercial products or reference to commercial organizations is for information only; it does not imply recommendation or endorsement by NIST, nor does it imply that the products mentioned are necessarily the best available for the purpose. ## Additional Information\n\nFor additional information on NIST's Computer Security Division programs, projects and publications, visit the Computer Security Resource Center, csrc.nist.gov. Information on other efforts at NIST and in the Information Technology Laboratory (ITL) is available at www.nist.gov and www.nist.gov/itl."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does System and Network Security Acronyms and Abbreviations provide?"}, {"role": "assistant", "content": "\n\nNIST Interagency Report 7581 September 2009\n\n## System and Network Security Acronyms and Abbreviations\n\nKaren Scarfone Victoria Thompson\n\nNIST Interagency Report 7581 September 2009\n\nSystem and Network Security Acronyms and Abbreviations\n\nKaren Scarfone Victoria Thompson\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nSeptember 2009\n\n\n\nU.S. Department of Commerce\n\nGary Locke, Secretary\n\nNational Institute of Standards and Technology\n\nPatrick D. Gallagher, Deputy Director\n\n## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical 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 Interagency Report discusses ITL's research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Interagency Report 7581 32 pages (Sep. 2009)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "System and Network Security Acronyms and Abbreviations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n3.1.1. 3.1.1), purge (see Sec. 3.1.1."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Trustworthy Email:\n\n�e 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 costeffective security and privacy of other than national s ecurity-related information in federal information systems. �e Special Publication 800 -series reports on ITL's research, guidelines, and outreach efforts in informat ion system security, and its collaborative activities with industry, government, and academic organizations.\n\nIn addition to MUAs and MTAs , there are other network components used to suppo rt the email service for an organization. Most obviously is the physical infrastructure: the cables, wireless access points, routers and switches that make up the network . In addition, there are network components used by email components in the process of completing their tasks . �is includes the DNS , Public Key Infrastructure (PKI), and network security components that are used by the organization.\n\nfor physical harm or for committing financial fraud) is called phishing. From the above discussion of email bombing attacks, it should be clear that spam can sometimes be a type of email bombing."}], "metadata": {"source": "Trustworthy Email", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Guide to Security for Full Virtualization Technologies:\n\n1-1 | | | 1.1 | Authority.................................................................................................................1-1 | | | | 1.2 | Purpose and Scope................................................................................................1-1 | | | | 1.3 | Audience ................................................................................................................1-1 | | | | 1.4 | Document Structure ...............................................................................................1-1 | | | 2."}], "metadata": {"source": "Guide to Security for Full Virtualization Technologies", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n................................................................... | Executive Summary.................................................................................................................\n|\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| U.S. Government Vulnerability Disclosure..................................................................... | 2 | |\n| Usage of Document Terminology................................................................................ | 5 | |\n| Federal Vulnerability Disclosure Coordination Body .................................................... | 6 | |\n| Preparation................................................................................................................."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to ISCMA_ An Information Security Continuous Monitoring Program Assessment:\n\n| The Principal Assessment Workbook...................................................................."}], "metadata": {"source": "ISCMA_ An Information Security Continuous Monitoring Program Assessment", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Computer Security Training & Awareness Course Compendium:\n\n| CONTROL AND SECURITY OF LANS | 50 | |-------------------------------------------------------------------------------------|-----------------------------------------------------------------------| | DATA CENTER RECOVERY PLANNING (M2040) | 20 | | DATA COMMUNICATIONS SECURITY | 28 | | DATA SECURITY PLANNING: STRATEGIES FOR EFFECTIVE INFORMATION SECURITY (W9898) | 22 | | DATA SECURITY PLANNING | 68 | | DATABASE SECURITY SEMINAR | 65 | | DETECTING AND PREVENTING COMPUTER FRAUD | 11 | | DEVELOPING COMPUTER SECURITY POLICIES & PROCEDURES | 28 | | DISASTER RECOVERY PLANNING | 70 | | DISASTER RECOVERY PLANNING: STRATEGIES TO DEVELOP & MAINTAIN PROVABLE | DISASTER RECOVERY PLANNING: STRATEGIES TO DEVELOP & MAINTAIN PROVABLE | | RECOVERY CAPABILITY (W9912) | 20 | | EDI: New Frontiers For Auditors | 56 | | EDP AUDITING - CIS 433 | 78 | | EDP CONCEPTS FOR BUSINESS | 6 | | EDP AUDITING: THE FIRST STEP | 52 | | EXECUTIVE AIS SECURITY BRIEFING | 8 | | FEDERAL AIS COMPUTER SECURITY REQUIREMENTS | 4 | | FUNDAMENTALS OF COMPUTER SECURITY FOR FEDERAL INFORMATION SYSTEMS | 64 | | HOW TO MANAGE AN INFORMATION SECURITY PROGRAM: A GUIDE FOR NEWLY APPOINTED MANAGERS | 23 | | IMPLEMENTING & MANAGING A COMPUTER SECURITY PROGRAM | 19 | |"}], "metadata": {"source": "Computer Security Training & Awareness Course Compendium", "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 AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Guide to Information Technology Security Services:\n\n3.3.1 Review Risk Assessment and Security Plan\n\nThe Contractor shall review the appropriate <organization name> risk assessment and <organization name> security plan for the sensitive systems addressed by this SOW."}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Security Requirements for Cryptographic Modules:\n\nThis standard shall be used in designing and implementing cryptographic modules that federal departments and agencies operate or are operated for them under contract. The standard provides four increasing, qualitative levels of security intended to cover a wide range of potential applications and environments. The security requirements cover areas related to the secure design, implementation and operation of a cryptographic module. These areas include cryptographic module specification; cryptographic module interfaces; roles, services, and authentication; software/firmware security; operating environment; physical security; non-invasive security; sensitive security parameter management; self-tests; life-cycle assurance; and mitigation of other attacks. 1. Name of Standard. Security Requirements for Cryptographic Modules (FIPS PUB 140-3). 2. Category of Standard. Computer Security Standard, Cryptography. 3. Explanation. This standard specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system protecting sensitive but unclassified information (hereafter referred to as sensitive information). The standard provides four increasing, qualitative levels of security: Level 1, Level 2, Level 3, and Level 4. These levels are intended to cover the wide range of potential applications and environments in which cryptographic modules may be employed. The security requirements cover areas related to the secure design and implementation of a cryptographic module. These areas include cryptographic module specification; cryptographic module interfaces; roles, services, and authentication; software/firmware security; operating environment; physical security; non-invasive security; sensitive security parameter management; self-tests; life-cycle assurance; and mitigation of other attacks."}], "metadata": {"source": "Security Requirements for Cryptographic Modules", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4) provide? (Part 5)"}, {"role": "assistant", "content": "for Open System Interconnection (OSI) [4]. SP4 consists of a simple encapsulation/decapsulation protocol that protects normal Transport Protocol data units within a cryptographically secure envelope.\nSP4 is compliant with the security addendum to the OSI BRM [5], and forms the basis of the emerging ISO standard for a Transport Layer Security Protocol [6]. SP4 extends the OSI Transport connectionless and connection oriented standards [7,8] to provide or support the following security services defined in the security addendum:\n\n- (1) Data Integrity,\n- (2) Data Confidentiality,\n- (3) Data Origination Authentication, and\n- (4) Access Control. ## 1.2 Objectives\n\nThis report specifies the Protocol Implementation Conformance Statement (PICS) proforma for SP4. The supplier of a protocol implementation which is claimed to conform to the SDNS Standard [1] shall complete the SP4 PICS proforma. A completed PICS proforma becomes the PICS for the implementation in question. The PICS is a statement identifying the capabilities and options of the protocol that have been implemented. The PICS can serve a number of purposes, including as:\n\n- (1) a check list for the protocol implementer, to reduce the risk of failure to conform to the standard through oversight;\n\n- (2) a detailed indication for the supplier and receiver of the implementation of its capabilities, stated relative to the common basis of understanding provided by the standard PICS proforma;\n- (3) a basis for the user of the implementation to check the possibility of interworking with another implementation;\n- (4) the basis for a protocol tester to select appropriate tests against which to assess the claim for conformance of the implementation. The remainder of this report defines the procedures, format, and content that comprise the SP4 PICS proforma. The format is intended to follow the style used in the PICS proforma for the transport protocol [9]. Most of the content is derived directly from the SP4 standard [1]."}], "metadata": {"source": "Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to BIOS Protection Guidelines for Servers:\n\nserver motherboard. The Service Processor microcontroller runs a specialized operating system typically stored in flash memory, and provides administrators with an interface to manage the host server.\nThe Service Processor is typically a highly privileged component in modern servers, often capable of updating firmware and software on the system, changing configuration settings, and reading from system memory. This document assumes administrators will implement proper computer, network, and physical security controls to mitigate the unique risks to Service Processors. For instance, typically administrators interact with the Service Processor over a network interface. Security best practices dictate that the Service Processor should be on a private LAN accessible only to system administrators."}], "metadata": {"source": "BIOS Protection Guidelines for Servers", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Managing the Security of Information Exchanges:\n\n| ...........................................................................................................\n3 |\n| 2.1 Information Exchange ....................................................................................................4 | |\n| 2.1.1 System Interconnections ....................................................................................5 | |\n| 2.1.2 Methods of Information Exchange | .....................................................................7 |\n| 2.2 Information Exchange: Accessing or Transferring the Information................................8 | |\n| 3 Information Exchange Security Management................................................................... | 9 |\n| 3.1."}], "metadata": {"source": "Managing the Security of Information Exchanges", "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 Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\n- DevSecOps pipelines are involved in building, checking in, and checking out from a container registry called Iron Bank, a repository of DOD-vetted hardened container images.\n- The Air Force's Platform One, the DevSecOps platform that enabled the concept of continuous authority to operate (C-ATO), which in turn streamlined the DOD's authorization process to accommodate the speed and frequency of modern continuous software deployments.\n- The National Geospatial-Intelligence Agency (NGA) outlined its DevSecOps strategy in 'The NGA Software Way,' where three key metrics - availability, lead time, and deployment frequency - are laid out for each of its software products, along with specification of seven distinct product lines for enabling DevSecOps pipelines, including messaging and workflow tools.\n- The Centers for Medicare and Medicaid Services (CMS) is adopting a DevSecOps approach where one emphasis is on laying the groundwork for the software bill of materials (SBOM) - a formal record that contains the details and supply chain relationships of various components used in building software. The purpose of producing SBOMs is to meet the goals established under the Continuous Diagnostics and Mitigation (CDM) program.\n\n| Policy Category | Example Policies |\n|-----------------------------------|-------------------------------------------------------------------------------------|\n| | • Ensure that policies of all types do not have conflicts |\n| Supply chain policies | • Allow only approved container registries • Allow only certified libraries |\n| Audit and accountability policies | • Ensure that there are policies associated with audit and accountability functions |"}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "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 IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\nThis section presents background information about IoT devices that organizations should consider in their device acquisition processes. This publication draws from other NIST guidance, namely the Risk Management Framework (RMF) [800-37], the Cybersecurity Framework (CSF) [CSF], and NIST SP 800-161, Cyber Supply Chain Risk Management Practices for Systems and Organizations [800-161]. Organizations familiar with this guidance and the context of IoT devices within a system could skip this section. It is expected that organizations will follow the RMF steps to manage risk to the system and organization throughout the system development life cycle. As IoT devices are introduced to the system, often after it is in operation, it is critical to consider the security impact of such changes. Since IoT devices will often be integrated into existing systems, this publication will provide guidance for organizations in the context of the RMF. Considering an IoT device as an enabling or other system does not alleviate all cybersecurity considerations on the part of an organization. The IoT device will still exist in another authorization boundary, which may or may not be managed by organizations that do not necessarily use the RMF (e.g., the manufacturer of the device, third-party service provider). That organization (i.e., that manages the IoT device within their authorization boundary) would have to be responsible for many aspects of risk management related to the IoT device, but any organization that uses the IoT device directly, services it provides, and/or its data will have responsibilities related to cybersecurity of that IoT device and its data. Readers of this document should refer to NIST SP 800-161 Revision 1, Cyber Supply Chain Risk Management Practices for Systems and Organizations [800-161] to understand these responsibilities and supporting practices."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does A Review of U.S. and European Security Evaluation Criteria provide? (Part 2)"}, {"role": "assistant", "content": "RUSTED INTERPRETATION | NETWORK | | |\n| 4 . 0 | TRUSTED MANAGEMENT SYSTEM INTERPRETATION ...\n| DATABASE | | |\n| 5.0 | IT SECURITY CRITERIA - CRITERIA FOR THE EVALUATION OF THE TRUSTWORTHINESS OF INFORMATION TECHNOLOGY (IT) SYSTEMS | | | |\n| 6 . 0 | DRAFT TECHNOLOGY SECURITY EVALUATION CRITERIA | INFORMATION | | |\n| 7.0 | ANALYSIS OF SECURITY CRITERIA SETS ... | AND COMPARISON | | |\n| 7.1 | U.S. EVALUATION CRITERIA - ORANGE BOOK, RED BOOK, | SECURITY TDI | | |\n| 7.2 | U.S. SECURITY EVALUATION CRITERIA | vs. EUROPEAN | | |\n| 8.0 | TRUSTED TECHNOLOGY | SYSTEM | | |\n| 9.0 | FUTURE IN THE DEVELOPMENT OF SECURITY | U.S."}], "metadata": {"source": "A Review of U.S. and European Security Evaluation Criteria", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Computer Security Division 2004 Annual Report:\n\nSecurity accreditation is the official management decision to authorize operation of an information system. This authorization, given by a senior agency official, is applicable to a particular environment of operation and explicitly accepts the risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals, remaining after the implementation of an agreed upon set of security controls. By accrediting an information system, the agency official is not only responsible for the security of the system but is also accountable for adverse impacts to the agency if a breach of security occurs. Security accreditation, which is required under OMB Circular A-130, provides a form of quality control and challenges managers and technical staff at all levels to implement the most effective security controls and techniques, given technical constraints, operational constraints, cost and schedule constraints and mission requirements. In addition to risk assessments and security plans, security evaluation also plays an important role in the security accreditation process. It is essential that agency officials have the most complete, accurate and trustworthy information possible on the security status of their information systems in order to make credible, risk-based decisions on whether to authorize operation of those systems. This information and supporting evidence for system authorization is often developed during a detailed security review of the information system, typically referred to as security certification . Security certification is the comprehensive evaluation of the management, operational and technical security controls in an information system."}], "metadata": {"source": "Computer Security Division 2004 Annual Report", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Cyber Threat Information Sharing:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to 2017 NIST_ITL Cybersecurity Program Annual Report:\n\nThe 2016 Annual Report, the National Initiative for Cybersecurity Education (NICE) Cybersecurity Workforce Framework, attribute-based access control and access control standards and policies, application container security, Secure Hash Algorithm-3 (SHA-3) derived functions, cybersecurity event recovery, data integrity, recovering from ransomware and other destructive events, securing Apple OS X 10.10 systems, protecting controlled unclassified information in nonfederal information systems and organizations, systems security engineering, cyber threat information sharing, bluetooth security, the National Checklist Program, digital identity guidelines, block cipher modes of operation, the Cipher-Based Message Authentication Code (CMAC) - a Mode for Authentication, an introduction to information security, a report of the workshop on software measures and metrics to reduce security vulnerabilities, platform firmware resiliency, fog computing, de-identifying government datasets, Long Term Evolution (LTE) security, trustworthy email, security recommendations for hypervisor deployment, the Triple Data Encryption Algorithm (TDEA) Block Cipher, key-derivation methods in key-establishment schemes, pair-wise key-establishment schemes using discrete logarithm cryptography, security and privacy controls, a risk management framework for information systems and organizations, personal identity verification (PIV) credentials, access rights management for the financial services sector, securing wireless infusion pumps in healthcare delivery organizations, situational awareness for electric utilities, and domain name systemsbased electronic mail security."}], "metadata": {"source": "2017 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\n| Audience.........................................................................................................\n| 2 |\n| | Document Structure........................................................................................ | 3 |\n| 2. Process-based Manufacturing System Low Impact Level Use Case ...............4 | 2. Process-based Manufacturing System Low Impact Level Use Case ...............4 | 2. Process-based Manufacturing System Low Impact Level Use Case ...............4 |\n| | Introduction ..................................................................................................... | 4 |\n| | Process-based Low Impact Level Use Case | .................................................. 4 |\n| 3. Policy and Procedure Implementations...............................................................9 | 3."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Computer Security Division 2010 Annual Report:\n\nSecurity and Health Information Technology National Initiative for Cybersecurity Education (NICE) | 9 14 | Access Control and Privilege Management Research Security for Grid and Pervasive Systems Security Ontologies: Modeling Quantitative Risk Analysis Enterprise Systems Protecting | 31 | | | 13 | NIST Cloud Computing Project Policy Machine | | | Security Practices and Policies Small and Medium Size Business Outreach | 12 12 | Automated Combinatorial Testing for Software Conformance Verification for Access Control Policies Forensics forWeb Services Mobile Handheld Device Security and Forensics | 31 32 33 33 | | | 11 11 | | | | | | | 34 | | | | | 35 35 36 | | Smart Grid Cyber Security | | | | | | | Virtualization Technologies Cloud Computing andVirtualization Laboratory | 36 36 36 | | Supply Chain Risk Management | 15 | | | | Cryptographic Validation Programs and Laboratory | 15 | Access Control and Identitiy Management in Virtualized Systems | 37 37 38 38 | | Accreditation Cryptographic ModuleValidation Program and Cryptographic | 16 16 17 18 | Security Content Automation Protocol (SCAP) National Vulnerability Database National Checklist Program Security Content Automation Protocol Validation Program |"}], "metadata": {"source": "Computer Security Division 2010 Annual Report", "cmmc_level": "2", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Information Security Handbook_ A Guide for Managers:\n\nractor an identification credential, and also by specifying the electronic and physical properties of the credential itself. The HSPD-12 credential is known as the Personal Identity Verification card.\n| CLASS | FAMILY | IDENTIFIER |\n|-------------|--------------------------------------------------------|--------------|\n| Management | Risk Assessment | RA |\n| Management | Planning | PL |\n| Management | System and Services Acquisition | SA |\n| Management | Certification, Accreditation, and Security Assessments | CA |\n| Operational | Personnel Security | PS |\n| Operational | Physical and Environmental Protection | PE |\n| Operational | Contingency Planning | CP |\n| Operational | Configuration Management | CM |\n| Operational | Maintenance | MA |\n| Operational | System and Information Integrity | SI |\n| Operational | Media Protection | MP |\n| Operational | Incident Response | IR |\n| Operational | Awareness and Training | AT |\n| Technical | Identification and Authentication | IA |\n| Technical | Access Control | AC |\n| Technical | Audit and Accountability | AU |\n| Technical | System and Communications Protection | SC |"}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice PL.L2-3.15.6 (NIST 3.15.6)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.15.6. 3.15.6."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "nist_control": "3.15.6", "cmmc_practice_id": "PL.L2-3.15.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0:\n\nThe Respond Function supports the ability to contain the impact of a potential cybersecurity event. Examples of outcome Categories within this Function include: Response Planning; Communications; Analysis; Mitigation; and Improvements. The Recover Function supports timely recovery to normal operations to reduce the impact from a cybersecurity event. Examples of outcome Categories within this Function include: Recovery Planning; Improvements; and Communications."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to PIV Card to Reader Interoperability Guidelines:\n\nThe purpose of this document is to present recommendations for Personal Identity Verification (PIV) card readers in the area of performance and communications characteristics to foster interoperability. This document is not intended to re-state or contradict requirements specifically identified in Federal Information Processing Standard 201 (FIPS 201) or its associated documents. It is intended to augment existing standards to enable agencies to achieve the interoperability goal of Homeland Security Presidential Directive 12 (HSPD-12).\n\nAt a minimum, the contact interface shall support all card commands for contact based access specified in Section 7, End-point PIV Card Application Card Command Interface of SP 800-73-1, Interfaces for Personal Identity Verification.\n\nAt a minimum, the contactless interface shall support all card commands for contactless based access specified in Section 7, End-point PIV Card Application Card Command Interface of SP 800-73-1, Interfaces for Personal Identity Verification."}], "metadata": {"source": "PIV Card to Reader Interoperability Guidelines", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Information Security Guide for Government Executives provide? (Part 3)"}, {"role": "assistant", "content": "an effective information security program? - What are the information security laws, regulations, standards, and guidance that I need to understand to build an effective information security program?\n- Where can I learn more to assist me in evaluating the effectiveness of my information security program? This guide provides the answers to those questions. ## Acknowledgements\n\nNIST would like to thank the many people who assisted with the development of this NIST Interagency Report (NISTIR). NIST management officials who supported this effort include: Joan Hash, William C. Barker, Elizabeth Chew, and Matthew Scholl. The authors would like to thank Marianne Swanson, Jaren Doherty, and James St. Pierre, who assisted with reviewing this document and provided comments and suggestions for improvement. The authors would also like to thank Tanya Brewer for her extensive editing work. In addition, special thanks are due those contractors who helped craft the Executive Guide NISTIR, prepare drafts, and review materials:\n\nNadya Bartol, of BAH, served as Project Manager for BAH on this project. In addition, other BAH employees contributed to the NISTIR, including Marge Spanninger and Sedar Labarre. The authors also gratefully acknowledge and appreciate the many contributions from individuals in the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication. ## Introduction\n\nInformation Security for Government Executives provides a broad overview of information security program concepts to assist senior leaders in understanding how to oversee and support the development and implementation of information security programs."}], "metadata": {"source": "Information Security Guide for Government Executives", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Biometric Specifications for Personal Identity Verification:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST. 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. Homeland Security Presidential Directive HSPD-12, Policy for a Common Identification Standard for Federal Employees and Contractors [HSPD-12], called for Homeland Security Presidential Directive HSPD-12, Policy for a Common Identification Standard for Federal Employees and Contractors [HSPD-12], called for new standards to be adopted governing interoperable use of identity credentials to allow physical and logical access to Federal government locations and systems."}], "metadata": {"source": "Biometric Specifications for Personal Identity Verification", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\n• Design Definition\n• System Analysis\n• Implementation\n• Integration\n• Verification\n• Transition\n• Validation\n• Operation\n• Maintenance\n• Disposal\n\nDuring the Retirement stage, system elements or the entire system of interest are removed\nfrom operations. The retirement process can affect other systems with which the system of\ninterest interacts and can decrease the cyber resiliency of those systems and of the supported\nmission or business processes. Retirement strategies can include phased removal of system\nelements, turnkey removal of all system elements, phased replacement of system elements, and\nturnkey replacement of the entire system of interest. Cyber resiliency objectives and priorities\nare identified for the systems, missions, and business functions in the operational environment\nto inform analysis of the potential or expected effects of different retirement strategies on the\nability to achieve those objectives. Like the support stage, the retirement stage can introduce\nsignificant vulnerabilities, particularly during disposal and unintended residue remaining from\ndecommissioned assets.33\n\n- Prioritize and tailor objectives for the environment of operation.\n- Ensure that disposal processes enable those objectives to be achieved,\nmodifying or upgrading capabilities of other systems as necessary (Re-\nArchitect objective)."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering 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 is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.3.1 Education... 3.3.1 Education... 3.3.1 Education..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.3.2 Job Experience\n\n## Focus Groups\n\nIn the focus group demographic survey, we asked participants how many years they had worked as government employees, in their current organization, and in a cybersecurity role."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Secure Domain Name System (DNS) Deployment Guide provide? (Part 5)"}, {"role": "assistant", "content": "............................................................... 1 | Executive Summary.................................................................................................................\n1 | Executive Summary................................................................................................................. 1 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| Changes in this Document...................................................................................................... | Changes in this Document...................................................................................................... | 4 |\n| 1. Introduction.................................................................................................................... | 1. Introduction...................................................................................................................."}], "metadata": {"source": "Secure Domain Name System (DNS) Deployment Guide", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 for Security-Focused Configuration Management of Information Systems:\n\n3.5.1 Report Recipients\n\n3."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of Information Systems", "cmmc_level": "all", "nist_control": "3.5.1", "cmmc_practice_id": "IA.L2-3.5.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\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. Computer security; Cybersecurity Framework (CSF); distributed control systems (DCS); industrial control systems (ICS); information security; manufacturing; network security; programmable logic controllers (PLC); risk management; security controls; supervisory control and data acquisition (SCADA) systems. | Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi | Executive Summary..................................................................................................... vi |\n|----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction ............................................................................................................1 | 1."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\n| Asset Management Category..................................................................................13 | |\n| 5.1.2. | Business Environment Category.............................................................................19 | |\n| 5.1.3. | Governance Category | .............................................................................................23 |\n| 5.1.4. | Risk Assessment Category .....................................................................................26 | |\n| 5.1.5. | Risk Management Category....................................................................................29 | |\n| 5.1.6."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Guide to Storage Encryption Technologies for End User Devices:\n\n3.1.3 | File/Folder Encryption... 3.1.3 File/Folder Encryption\n\nFile encryption is the process of encrypting individual files on a storage medium and permitting access to the encrypted data only after proper authentication is provided."}], "metadata": {"source": "Guide to Storage Encryption Technologies for End User Devices", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\n| Executive Summary . . . . . . . . . . | Executive Summary . . . . . . . . . . | . . . . . . . . . . . | 1 |\n|----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1. Introduction . . . . . . . . . | 1. Introduction . . . . . . . . . | . . . . . . . . . . . . . . | 3 |\n| 1.1. Document Purpose and Scope | 1.1. Document Purpose and Scope | . . . . . . . . . | 7 |\n| 1.2. Intended Audience . . | 1.2. Intended Audience . . | . . . . . . . . . . . . . . | 7 |\n| 1.3. Organization . . . . | 1.3. Organization . . . . | . . . . . . . . . . . . . . . | 8 |\n| Introducing De-Identifcation . | Introducing De-Identifcation . | . . . . . . . . . . . . | 9 |\n| 2.1. Historical Context . . | 2.1. Historical Context . . | . . . . . . . . . . . . . . | 9 |\n| 2.2. Terminology . . . . | 2.2. Terminology . . . . | . . . . . . . . . . . . . . . . | 12 |\n| Governance and Management of Data De-Identifcation . . | Governance and Management of Data De-Identifcation . . | Governance and Management of Data De-Identifcation . . | 18 |\n| 3.1. Identifying the Goals and Intended Uses of De-Identifcation . . . . . | 3.1. Identifying the Goals and Intended Uses of De-Identifcation . . . . . | 3.1. Identifying the Goals and Intended Uses of De-Identifcation . . . . . | 18 |\n| 3.2. | Evaluating the Risks and Benefts That Arise from De-Identifed Data Re- leases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog:\n\n- Securely Provision: Risk Management, Systems Architecture, Systems Development\n- Operate and Maintain: Data Administration, Network Services, Systems Administration, Systems Analysis\n- Oversee and Govern: Cybersecurity Management, Executive Cyber Leadership, Program/Project Management and Acquisition\n- Protect and Defend: Cybersecurity Defense Analysis, Cybersecurity Defense Infrastructure Support, Incident Response, Vulnerability Assessment and Management\n\n1. Provide education that describes the details necessary for malicious code protection, detection and eradication. Information that may be necessary to provide, as determined by the manufacturer's assessment of cybersecurity risk created by the IoT device, include details and actions such as:\n- a. Providing education to IoT device customers for how to implement malicious code protection in the IoT device and associated systems, as well as within related systems entry and exit points, and how to detect and eradicate malicious code. - b. Providing education to IoT device customers for how to update the IoT device and related systems malicious code protection mechanisms when new releases are available, in accordance with organizational configuration management policy and procedures. - c. Providing training and awareness information to IoT device customers that describe newly identified vulnerabilities and threats (such as zero-day malware) for the associated IoT device. - d. If the IoT device manufacturer provides anti-malware for the associated IoT device, or if the IoT device has built-in anti-malware capabilities, the manufacturer should provide education to the IoT device customers describing how to use and/or configure malicious code protection mechanisms in IoT devices, supporting anti-malware tools, and related systems. - e. Providing education describing the operational impacts of the anti-malware activities on mission critical processes in the system where the IoT device is used. - f."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to 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 Level 1 require for Configuration Management?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n| Identify | Applicability to PNT | References (PNT-Specific) | |-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AM-1: Physical devices and systems within the organization are inventoried."}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out:\n\n| 11-7 |\n| III. | | APPLICATION SECURITY | Ill-l |\n| | A.\n| Overview | Ill-l |\n| | B. | Computer Security and Privacy Plan Preparation | |\n| | | (lAW OMB CIR 90-08) | III-4 |\n| | C. | Certification of a Sensitive System | 1 11-6 |\n| | D. | Contingency Planning | 111-10 |\n| | E. | Sensitive/Critical Application Review (SCAR) | 111-14 |\n| IV. | INSTALLATION SECURITY | INSTALLATION SECURITY | IV-1 |\n| | A. | Overview | IV-1 |\n| | B. | Risk Analysis of a System | IV-3 |\n| | C. | Disaster Recovery and Continuity of Operations Planning | IV-8 |\n| V. | COMPUTER SECURITY AWARENESS AND TRAINING | COMPUTER SECURITY AWARENESS AND TRAINING | V-1 |\n| | A. | Overview | V-1 |\n| | B. | Computer Security Awareness and Training | V-2 |\n| VI. | COMPUTER SECURITY INCIDENT RESPONSE | COMPUTER SECURITY INCIDENT RESPONSE | VI-1 |\n| | A. | Overview | VI- |\n| | B. | Incident Response Team | VI-2 |"}], "metadata": {"source": "Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out", "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 Access Control?"}, {"role": "assistant", "content": "According to Foundational Cybersecurity Activities for IoT Device Manufacturers:\n\nmight require safeguards not usually considered for conventional IT devices. IoT can also introduce complexities related to scale, which could make ongoing management and support of devices difficult.\n- Which data needs to be protected, what types of protection each instance of data needs (i.e., confidentiality, integrity, availability), and how strong that protection needs to be\n- How strongly an entity's identity needs to be authenticated before granting access if the entity is a human (e.g., PIN, password, passphrase, two-factor authentication) or system/device (e.g., API keys, certificates)\n- Whether data received by or inputted into the device needs to be validated (e.g., to confirm the legitimacy of an update, to restrict the ability of malformed data to bypass access controls)\n- How readily software updates can be reverted if a problem occurs (e.g., a rollback capability, an anti-rollback capability)"}], "metadata": {"source": "Foundational Cybersecurity Activities for IoT Device Manufacturers", "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 Networks of 'Things' provide? (Part 4)"}, {"role": "assistant", "content": "poral concerns, and elements of unknown pedigree with possible nefarious intent. These primitives are the basic building blocks for a Network of 'Things' (NoT), including the Internet of Things (IoT).\nThis document offers an underlying and foundational understanding of IoT based on the realization that IoT involves sensing, computing, communication, and actuation. The material presented here is generic to all distributed systems that employ IoT technologies (i.e., 'things' and networks). The expected audience is computer scientists, IT managers, networking specialists, and networking and cloud computing software engineers. To our knowledge, the ideas and the manner in which IoT is presented here is unique. ## Keywords\n\nInternet of Things (IoT); Network of Things (NoT); reliability; security; trust; trustworthiness, sensors; big data; composability; distributed system. ## Acknowledgment\n\nAppreciation is given to Matt Scholl, Dave Ferraiolo, Tim Grance, Irena Bojanova, Angelos Stavrou, Rick Kuhn, and Phil Laplante, for the encouragement and support to take on this task. Appreciation is also given to Constantinos Kolia (GMU) for the suggestions in Section 5, and to Svetlana Lukoyanova for the artwork."}], "metadata": {"source": "Networks of 'Things'", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n| Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce provide? (Part 4)"}, {"role": "assistant", "content": "Audience\n\nThe NICE Framework serves as a bridge between employers and education, training, and certification providers as well as a tool to help learners determine needs and demonstrate capabilities.\nA standardized approach to Competency Areas provides accessible information about what individuals need to know and be able to do, enables the development of more effective learning, and establishes regular processes to consistently describe and validate a learner's capabilities. Therefore, the following are both stakeholders and the audience for this work: employers; workforce development and human resources professionals; education, training, and certification providers; and learners. ## Document Conventions\n\nThe terms 'shall' and 'shall not' indicate requirements to be followed strictly in order to conform to the publication and from which no deviation is permitted. The terms 'should' and 'should not' indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. The terms 'may' and 'need not' indicate a course of action permissible within the limits of the publication. The terms 'can' and 'cannot' indicate a possibility and capability, whether material, physical or causal. Those seeking a career in cybersecurity or performing cybersecurity work-including students, job seekers, and employees-are referenced as Learners. This moniker highlights that each member of the workforce is also a lifelong learner. ## Note to Readers\n\nThis publication assumes existing knowledge of the Workforce Framework for Cybersecurity (NICE Framework) , NIST Special Publication 800-181, Revision 1, and is expected to be read in that context. This document was released in draft form for comment twice prior to this publication."}], "metadata": {"source": "NICE Framework Competency Areas_ Preparing a Job-Ready Cybersecurity Workforce", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Vetting the Security of Mobile Applications provide? (Part 4)"}, {"role": "assistant", "content": "00-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\nMobile applications are an integral part of our everyday personal and professional lives. As both public and private organizations rely more on mobile applications, ensuring that they are reasonably free from vulnerabilities and defects becomes paramount. This paper outlines and details a mobile application vetting process. This process can be used to ensure that mobile applications conform to an organization's security requirements and are reasonably free from vulnerabilities. ## Keywords\n\napp vetting; app vetting system; malware; mobile applications; mobile security; NIAP; security requirements; software assurance; software vulnerabilities; software testing. ## Trademark Information\n\nAll registered trademarks belong to their respective organizations."}], "metadata": {"source": "Vetting the Security of Mobile Applications", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines on Firewalls and Firewall Policy:\n\nt the Transmission Control Protocol/Internet Protocol (TCP/IP) layers that each is able to examine. TCP/IP communications are composed of four layers that work together to transfer data between hosts.\nWhen a user wants to transfer data across networks, the data is passed from the highest layer through intermediate layers to the lowest layer, with each layer adding more information. The lowest layer sends the accumulated data through the physical network, with the data then passed upwards through the layers to its destination. Simply put, the data produced by a layer is encapsulated in a larger container by the layer below it. The four TCP/IP layers, from highest to lowest, are shown in Figure 2-1."}], "metadata": {"source": "Guidelines on Firewalls and Firewall Policy", "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 Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.:\n\nThe E2E Framework is governed by the security council, which is composed of cross-functional senior management from product engineering, product line management, information security, product security, supply chain risk and compliance (SCRC), facility safety and security, and legal. Quarterly security council meetings direct the implementation schedule for individual contributors from each function. While framework-based planning is a cross-functional exercise, the resulting controls are ultimately owned and operated by each function."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "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 Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies:\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. Office of Management and Budget Circular A-130 4 establishes general policy for the planning, budgeting, governance, acquisition, and management of Federal information, personnel, equipment, funds, IT resources and supporting infrastructure and services. The appendices to this Circular also include responsibilities for protecting Federal information resources and managing personally identifiable information (PII). The requirements of this Circular apply to the information resources management activities of all agencies of the Executive Branch of the Federal Government. The requirements of Circular A-130 apply to management activities concerning all information resources in any medium (unless otherwise noted), including paper and electronic information. When an agency acts as a service provider, the ultimate responsibility for compliance with applicable requirements of this Circular is not shifted (to the service provider). Agencies are required to describe the responsibilities of service providers in relevant agreements with the service providers. Agencies are not required to apply this Circular to national security systems (defined in 44 U.S.C. § 3552 5 ), but are encouraged to do so where appropriate. For national security systems, agencies shall follow applicable statutes, executive orders, directives, and internal agency policies."}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies", "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 Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI):\n\n| IAT = Processes | IAT = Processes | IAT = Processes | IAT = Processes | IAT = Processes | |------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------------| | Authorization Focus Area | Identifier | Issuer Control | Applicability | Source | | Issuance/ Activation Process | AI(DC)-5 | A mechanism to block use of the Derived PIV Authentication private key after a number of consecutive failed authentication attempts is implemented."}], "metadata": {"source": "Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)", "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 Guidelines on Security and Privacy in Public Cloud Computing:\n\n| Purpose and Scope....................................................................................................\n| 1 |\n| 1.3 | Audience .................................................................................................................... | 1 |\n| 1.4 | Document Structure.................................................................................................... | 2 |\n| 2. | Background....................................................................................................................... 3 | Background....................................................................................................................... 3 |\n| 2.1 | Deployment Models...................................................................................................."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Framework Version 1.1 Manufacturing Profile provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. All NIST Computer Security Division publications, other than the ones noted above, are available at http://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 Email: CSF\\_Manufacturing\\_Profile@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\nThis document provides the Cybersecurity Framework (CSF) Version 1.1 implementation details developed for the manufacturing environment."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations:\n\n| Allocation [NISTIR 7298] | The process an organization employs to determine whether security controls are defined as system -specific, hybrid, or common. |\n|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Allocation [NISTIR 7298] | The process an organization employs to assign security controls to specific information system components responsible for providing a particular security capability (e.g., router, server, remote sensor). |\n| Application [NISTIR 7298] | A software program hosted by an information system. |\n| Assessment | See Security Control Assessment . |\n| Assessment Findings [NISTIR 7298] | Assessment results produced by the application of an assessment procedure to a security control or control enhancement to achieve an assessment objective; the execution of a determination statement within an assessment procedure by an assessor that results in either a satisfied or other than satisfied condition. |\n| Assessment Method [NISTIR 7298] | One of three types of actions (examine, interview, test) taken by assessors in obtaining evidence during an assessment. |\n| Assessment Object [NISTIR 7298] | The item (specifications, mechanisms, activities, individuals) upon which an assessment method is applied during an assessment. |\n| Assessment Objective [NISTIR 7298] | A set of determination statements that expresses the desired outcome for the assessment of a security control or control enhancement. |\n| Assessment Procedure [NISTIR 7298] | A set of assessment objectives and an associated set of assessment methods and assessment objects ."}], "metadata": {"source": "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Science Challenges:\n\n- Anti-forensics (e.g., obfuscation, data hiding, malware). Anti-forensics are a set of techniques used specifically to prevent or mislead forensic analysis. Anti-forensic challenges in cloud forensics include:\n- o The use of obfuscation, malware, data hiding, or other techniques to compromise the integrity of evidence\n- o Malware may circumvent virtual machine isolation methods\n- Incident first responders (e.g., trustworthiness of cloud Providers, response time, reconstruction). Incident first responder challenges in cloud forensics include:\n- o Confidence, competence, and trustworthiness of the cloud Providers to act as first responders and perform data collection\n- o Difficulty in performing initial triage\n- o Processing a large volume of collected forensic artifacts\n- Role management (e.g., data owners, identity management, users, access control). Role management challenges in cloud forensics include:\n- o Uniquely identifying the owner of an account\n- o Decoupling between cloud user credentials and physical users\n- o Ease of anonymity and creating fictitious identities online\n- o Determining exact ownership of data\n- o Authentication and access control\n- Legal (e.g., jurisdictions, laws, service level agreements, contracts, subpoenas, international cooperation, privacy, ethics) . Legal challenges in cloud forensics include:\n- o Identifying and addressing issues of jurisdictions for legal access to data\n- o Lack of effective channels for international communication and cooperation during an investigation\n- o Data acquisition that relies on the cooperation of cloud Providers, as well as their competence and trustworthiness\n- o Missing terms in contracts and service level agreements\n- o Issuing subpoenas without knowledge of the physical location of data\n- Standards (e.g., standard operating procedures, interoperability, testing, validation)."}], "metadata": {"source": "NIST Cloud Computing Forensic Science 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 does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations:\n\nreamline incident communications and reporting. 3. Engagement of executive leadership in C-SCRM: Executives and Boards of Directors are engaged in C-SCRM through regular presentations and touchpoints.\nSuch engagement demonstrates leadership commitment and importance of C-SCRM to the organization. 4. C-SCRM is driven by business priorities to ensure product and service delivery: CSCRM is considered one of the critical capabilities that reduce the risks of disruption to product and service delivery if an incident were to occur. Organizations shared a variety of practices on how they identify, prioritize, and respond to cyber supply chain risks."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Summary of Findings and Recommendations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\nAs subject attributes may be provisioned by different authorities (e.g., human resources , security , organization leadership , etc.), methods for obtaining authoritative data must be regulated. For example, only security authorities should be able to provision and assert clearance attributes and attribute values based on authoritative personnel clearance information; an individual should not be able to alter his or her own clearance attribute value. Other subject attributes may involve the subject's current tasking, physical location, and the device from which a request is sent. Processes need to be developed to assess and assure the quality of such subject attribute data."}], "metadata": {"source": "Attribute Considerations for Access Control 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 Attribute-based Access Control for Microservices-based Applications using a Service Mesh provide? (Part 3)"}, {"role": "assistant", "content": "h to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nAll NIST Computer Security Division publications, other than the ones noted above, are available at http://csrc.nist.gov/publications. ## Comments on this publication may be submitted to:\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nEmail: sp800-204b-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\nDeployment architecture in cloud-native applications now consists of loosely coupled components, called microservices, with all application services provided through a dedicated infrastructure, called a service mesh, independent of the application code."}], "metadata": {"source": "Attribute-based Access Control for Microservices-based Applications using a Service Mesh", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.2 (NIST 3.4.2)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.4.2. 3.4.2 and\nSec. 3.4.2 and\nSec."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "nist_control": "3.4.2", "cmmc_practice_id": "CM.L2-3.4.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\nFew software development life cycle (SDLC) models explicitly address software security in detail, so secure software development practices usually need to be added to each SDLC model to ensure that the software being developed is well-secured. This document recommends the Secure Software Development Framework (SSDF) - a core set of high-level secure software development practices that can be integrated into each SDLC implementation. Following such practices should help software producers reduce the number of vulnerabilities in released software, reduce the potential impact of the exploitation of undetected or unaddressed vulnerabilities, and address the root causes of vulnerabilities to prevent future recurrences. Because the framework provides a common vocabulary for secure software development, software acquirers can also use it to foster communications with suppliers in acquisition processes and other management activities. This document provides a common language to describe fundamental secure software development practices. This is similar to the approach taken by the Framework for Improving Critical Infrastructure Cybersecurity , also known as the NIST Cybersecurity Framework [NISTCSF]. 2 Expertise in secure software development is not required to understand the practices."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines for Securing Wireless Local Area Networks (WLANs):\n\nitoring, WLAN-specific vulnerability monitoring involves analyzing WLAN communications and identifying policy violations, such as communications using the wrong protocols, encryption key lengths, etc.\nThis is effective at identifying misconfigured WLAN devices as well as devices that are acting differently than their configuration indicates. It is especially helpful when not all of the WLAN devices are under the organization's control, such as visitor laptops, and when unauthorized WLAN devices are a concern (e.g., an employee attaching a personal mobile device to an organization WLAN without authorization). This form of vulnerability monitoring is often provided by the same tools that are effective at attack monitoring, as explained in Section 3.2."}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\nSession resumption considerations and server recommendations were given in Section 3.6. There are no specific recommendations for clients regarding session resumption when using TLS 1.2, 1.1, or 1.0. Clients typically will not know if any anti-replay mechanisms are in place to prevent replay attacks on 0-RTT data in TLS 1.3. Therefore, clients using TLS 1.3 should not send 0RTT data."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "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 Proxy Validation and Verification for Critical AI Systems_ A Proxy Design Process:\n\n1. Chemical: Basic chemicals, specialty chemicals, agricultural chemicals, and consumer products\n2. Commercial facilities: Entertainment/media, gaming, lodging, outdoor events, public assembly, real estate, retail, and sports leagues\n3. Communications: Providers of voice services using interconnected terrestrial, satellite, and wireless transmission systems\n4. Critical manufacturing: Metals; machinery; electrical equipment, appliances, and components; and transportation equipment\n5. Dams: Critical water retention and control services\n6. Defense industrial base: Research, development, production, delivery, and maintenance of military weapons systems, subsystems, and components or parts to meet U.S. military requirements\n7. Emergency services: Highly skilled and trained personnel and physical and cyber resources that provide prevention, preparedness, response, and recovery services during day-to-day operations and incident response\n8. Energy: Electricity, oil, and natural gas\n9. Financial services: Depository institutions, providers of investment products, insurance companies, other credit and financial organizations, and providers of critical financial utilities and services that support these functions"}], "metadata": {"source": "Proxy Validation and Verification for Critical AI Systems_ A Proxy Design Process", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Maintenance?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures provide? (Part 3)"}, {"role": "assistant", "content": "ght, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-11-04 Supersedes NIST SP 800-55 Rev.\n1 (July 2008) https://doi.org/10.6028/NIST.SP.800-55r1\n\n## How to Cite this NIST Technical Series Publication:\n\nSchroeder K, Trinh H, Pillitteri VY (2024) Measurement Guide for Information Security: Volume 1 - Identifying and Selecting Measures. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-55v1. https://doi.org/10.6028/NIST.SP.800-55v1\n\n## Author ORCID iDs\n\nKatherine Schroeder: 0000-0002-4129-9243 Hung Trinh: 0000-0002-3323-0836 Victoria Yan Pillitteri: 0000-0002-7446-7506\n\n## Contact Information\n\ncyber-measures@list.nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/55/v1/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis document provides guidance on how an organization can develop information security measures to identify the adequacy of in-place security policies, procedures, and controls. It explains the measures prioritization process and how to evaluate measures. ## Keywords\n\nassessment; information security; measurement; measures; metrics; performance; qualitative; quantitative; reports; security controls. ## 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": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance:\n\n| |---------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| | 1.1 | Purpose.........................................................................................................................2 | | | 1.2 | Requirement Terms......................................................................................................3 | | | 1.3 | General Protocol Considerations .................................................................................3 | | | | 1.3.1 Mandatory-to-Implement versus Optional-to-Implement | .....................................4 | | 1.3.2 | Cryptographic Negotiation | ....................................................................................4 | | 1.3.3 | Single or Multi-Use Keys......................................................................................6 | | | | 1.3.4 Algorithm and Key Size Transition.......................................................................6 | | | 2 | Public Key Infrastructure (PKI) ........................................................................."}], "metadata": {"source": "Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cloud Computing Synopsis and Recommendations:\n\n| | 8.5.3 | System Integrity ......................................................................................... | 8-8 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------|\n| | 8.5.4 | Multi-tenancy ............................................................................................. | 8-8 |\n| | 8.5.5 | Browsers.................................................................................................... | 8-9 |\n| | 8.5.6 | Hardware Support for Trust........................................................................"}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "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 Incident Response?"}, {"role": "assistant", "content": "According to Fiscal Year 2024 Cybersecurity and Privacy Annual Report:\n\nnder, and the National Software Reference Database added data from 10,000+ new or updated applications (totaling over 42 million files) to assist with computer security and digital forensics analysis.\n- NIST published CSWP 36, Applying 5G Cybersecurity and Privacy Capabilities: Introduction to the White Paper Series ; CSWP 36A, Protecting Subscriber Identifiers with Subscription Concealed Identifier (SUCI): Applying 5G Cybersecurity and Privacy Capabilities ; CSWP 36B, Using Hardware-Enabled Security to Ensure 5G System Platform Integrity: Applying 5G Cybersecurity and Privacy Capabilities ; and CSWP 36C, Reallocation of Temporary Identities: Applying 5G Cybersecurity and Privacy Capabilities ."}], "metadata": {"source": "Fiscal Year 2024 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security Recommendations for Server-based Hypervisor Platforms:\n\n.). - HY-BF3: Direct Execution of commands from Guest VMs - Certain commands from Guest OSs are executed directly by the hypervisor instead of being triggered through interrupts and context switching.\nThis function applies to hypervisors that have implemented para-virtualization instead of full virtualization\n- HY-BF4: VM Lifecycle Management - All functions including creation and management of VM images, control of VM states (Start, Pause, Stop), VM migration, making snapshots, VM monitoring, and policy enforcement\n- HY-BF5: Management of hypervisor platform - Defining artifacts and setting values for various configuration parameters in hypervisor software modules including those for configuration of a Virtual Network inside the hypervisor and updates and patching to those modules."}], "metadata": {"source": "Security Recommendations for Server-based Hypervisor Platforms", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to General Server Security:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 |\n|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guide to General Server Security", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Report of the Workshop on Cryptography in Support of Computer Security:\n\ncomments and brief presentations. Professor Julian Bigelow, Institute for Advanced Studies at Princeton, welcomed the participants to the workshop and outlined the workshop objectives. Dr. Ruth Davis, Director of the Institute for Computer Sciences and Technology, gave an overview of the development process of the proposed Data Encryption Standard (DES). Technical presentations by ICST members and other workshop participants provided descriptions of the DES and how it may be used in computer systems.\n\nKONHEIM ( IBM ) : IBM did estimate those costs, but we neglected to include the cost of development.\n\nTUCHMAN ( IBM ) : My personal opinion is that if IBM were to build such a key searching machine consisting of a million special purpose chips, the development and production costs alone would result in a cost to the manufacturer an order of magnitude larger than the 20 million dollar figure that was estimated by Martin Heilman. The resulting machine would produce one key a day but would not be delivered before 1981 and the probability of success would be very low. IBM has no intention of building such a machine and I do not believe anyone would attempt to build such a machine."}], "metadata": {"source": "Report of the Workshop on Cryptography in Support 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 System and Services Acquisition?"}, {"role": "assistant", "content": "According to A Threat Analysis on UOCAVA Voting Systems:\n\ne for citizens overseas. In addition, registration and ballot requests can also take advantage of these distribution methods, but there are more threats when handling personal information from voters.\nVoted ballot return remains a more difficult issue to address, however emerging trends and developments in this area should continue to be studied and monitored."}], "metadata": {"source": "A Threat Analysis on UOCAVA Voting Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface:\n\n- The front matter describes configuration management recommendations.\n- o Section 1.3 specifies the effective date of SP 800-73-5.\n- The front matter also specifies NPIVP conformance testing procedures.\n- Appendix G provides the full Revision History of SP 800-73.\n\nSP 800-73-5 Parts 2 and 3 define two interfaces to an ICC that contain the PIV Card Application: a low-level card command interface (Part 2) and a high-level client API (Part 3). SP 800-73-5 Part 3 is optional, and NIST Personal Identity Verification Program (NPIVP) conformance testing for PIV Middleware in accordance with SP 800-73 Part 3 is discontinued since endpoints support high-level client API natively at the time of this publication."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio:\n\n| Function | Category | Subcategory | Implementation Example | |------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | GV.OV-5: Risk is identified, adjudicated, and tracked by risk management programs according to published formats."}], "metadata": {"source": "Information and Communications Technology (ICT) Risk Outcomes_ Integrating ICT Risk Management Programs with the Enterprise Risk Portfolio", "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 Approaches for Federal Agencies to Use the Cybersecurity Framework:\n\n| Benefit(s): • Facilitate communication among agency stakeholders, including executive leadership. • Facilitate a common language to inform and be informed by other risk management disciplines. | Primary SP 800-37 Level: 1 - Organization Primary Cybersecurity Framework Component: Core |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Summary: Using the Cybersecurity Framework's Functions (Identify, Protect, Detect, Respond, and Recover) as the basis for risk management dialogues related to the cybersecurity environment, organizations can raise awareness of cybersecurity and other risks to be managed and facilitate communication among agency stakeholders, including executive leadership. 4 This use example aggregates elements of the activities of uses 2-8."}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "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 Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines on Mobile Device Forensics:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Different mobile devices have different technical and physical characteristics (e.g., size, weight, processor speed, memory capacity). Mobile devices may also use different types of expansion capabilities to provide additional functionality. Furthermore, mobile device capabilities sometimes include those of other devices such as handheld Global Positioning Systems (GPS), cameras (still and video) or personal computers. Overall, mobile devices can be classified as feature phones that are primarily simple voice and messaging communication devices or smartphones that offer more advanced capabilities and services for multimedia, similar to those of a personal computer. Table 1 highlights the general hardware characteristics of feature and smartphone models, which underscore this diversity. A UICC can contain up to three applications: SIM, USIM and CSIM. UICCs used in GSM and UMTS mobile devices use the SIM and UMTS SIM (USIM) applications, while CDMA devices use the CSIM application."}], "metadata": {"source": "Guidelines on Mobile Device Forensics", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.4 (NIST 3.3.4)?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1:\n\n3.3.4 ISA 62443-3-3:2013 SR 3."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Biometric Specifications for Personal Identity Verification:\n\n| Introduction ..............................................................................................................................................1 | Introduction ..............................................................................................................................................1 | Introduction ..............................................................................................................................................1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 | Authority ....................................................................................................................................................... 1 | Authority ......................................................................................................................................................."}], "metadata": {"source": "Biometric Specifications for Personal Identity 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 Physical Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\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. through a physical connector. The vehicle communicates with vendor cloud/third-party organizations via Bluetooth, Wi-Fi, or cellular. - XFC/EVSE . Electric Vehicle Supply Equipment (EVSE) consists of systems that provide electric power to the vehicle to recharge the vehicle's batteries. EVSE systems include electrical conductors, related equipment such as Battery Energy Storage Systems (BESS), software, and communications protocols that deliver energy efficiently and safely to the vehicle. Extreme Fast Charging (XFC) is a type of EVSE that is capable of recharging vehicles in a manner of minutes rather than hours. [Energies-2019] In addition to connecting to the EV, the XFC/EVSE and related equipment must connect and communicate with cloud providers and third-party vendors for providing EVSE location information, billing, and other services. - Cloud/Third-Party Organizations . The EV/XFC ecosystem consists of independently owned and operated domains, and most charging stations are operated by a charging network with business models that blend station, electricity, and vehicle charging sales together. Third parties are individuals or entities that facilitate transactions but are not one of the primary parties within the exchange."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "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 A Threat Analysis on UOCAVA Voting Systems:\n\n| Ctrl. Number | Stages 4 RB BR | Stages 4 RB BR | Control Text | Notes: |\n|----------------|------------------|------------------|---------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| AC-2 | | X | ACCOUNTMANAGEMENT | IT systems used to manage registration information and interact with voters using telephone lines should be protected with access control mechanisms. |\n| AC-3 | | X | ACCESS ENFORCEMENT | IT systems used to manage registration information and interact with voters using telephone lines should be protected with access control mechanisms. |\n| AC-5 | | X | SEPARATION OF DUTIES | IT systems used to manage registration information and interact with voters using telephone lines should be protected with access control mechanisms. |\n| AC-6 | | X | LEAST PRIVILEGE | IT systems used to manage registration information and interact with voters using telephone lines should be protected with access control mechanisms."}], "metadata": {"source": "A Threat Analysis on UOCAVA Voting Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\nd like to acknowledge Tim Polk of NIST and Santosh Chokhani of CygnaCom Solutions, who were co-authors on the first revision of this document. We would also like to acknowledge Matthew J. Fanto and C.\nMichael Chernick of NIST and Charles Edington III and Rob Rosenthal of Booz Allen Hamilton who wrote the initial published version of this document."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Guidelines on Active Content and Mobile Code:\n\n3.3.2 Server-Oriented Attacks\n\nAttacks can be launched against Web server components and technologies as the first stage of a larger scheme."}], "metadata": {"source": "Guidelines on Active Content and Mobile Code", "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 Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile provide? (Part 4)"}, {"role": "assistant", "content": "h incorporating cybersecurity incident response recommendations and considerations throughout their cybersecurity risk management activities as described by the NIST Cybersecurity Framework (CSF) 2.0.\nDoing so can help organizations prepare for incident responses, reduce the number and impact of incidents that occur, and improve the efficiency and effectiveness of their incident detection, response, and recovery activities. Readers are encouraged to utilize online resources in conjunction with this document to access additional information on implementing these recommendations and considerations. ## Keywords\n\ncyber threat information sharing; Cybersecurity Framework; cybersecurity incident; cybersecurity risk management; incident handling; incident management; incident response. ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Supplemental Content\n\nNIST has established an Incident Response project page that hosts links to resources with additional information on incident response activities."}], "metadata": {"source": "Incident Response Recommendations and Considerations for Cybersecurity Risk Management_ A CSF 2.0 Community Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines provide? (Part 5)"}, {"role": "assistant", "content": "| | (U t4-l | ca tj •H u O O | ca | O C | (L) .O | Q | <1> 03 | | i-H !- | t+-i O to | e c •H !- ca rH tH e 4J 4) ca | ^1 C T3 (-1 | O 1- 1 +-» | | | 4^ | | cfl Z3 ^ 4> to 3 »-i | O *4-t | | | T3 rH • | rH MH | | U | ca c3 u | O C- ^ CMJ | | | E E | 3 t/i | rH c | | to (0 | | > O 1- 1 ti O C t-1 | 4) 'H | t/) | Q | 0 1) _r; (J | 0) •r4 M | | | \n\n## NISTIR 8333\n\n## Workshop Summary Report for 'Cybersecurity Risks in Consumer Home Internet of Things (IoT) Devices' Virtual Workshop\n\nKaterina N. Megas Michael Fagan Barbara Cuthill\n\nApplied Cybersecurity Division Information Technology Laboratory\n\nMary Raguso John Wiltberger The MITRE Corporation McLean, VA\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8333\n\nMarch 2021\n\n\n\nU.S. Department of Commerce Gina 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 8333 23 pages (March 2021)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8333\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Attribute-based Access Control for Microservices-based Applications using a Service Mesh:\n\nd for ubiquitous access to these applications from multiple remote locations using different types of devices, it is necessary to build the concept of zero trust [1] into this application environment.\nZero 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 based on asset ownership (enterprise or personally owned) [1]. Zero trust focuses on protecting resources (e.g., assets, services, workflows, and network accounts) rather than network segments since the network location is no longer seen as the prime component to the security posture of the resource. Furthermore, the loosely coupled nature of the components (i.e., microservices) of these cloud-native applications facilitates independent design, development, and agile deployment (e.g., Continuous Integration/ Continuous Delivery or Deployment (CI/CD) [2]) of the constituent microservices, enabling paradigms such as DevSecOps [3] (representing Development, Security and Operations) to be used."}], "metadata": {"source": "Attribute-based Access Control for Microservices-based Applications using a Service Mesh", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings:\n\na particular technology (e.g., mobile, semiconductors) to map the components of that technology to NIST-catalogued threats and countermeasures."}], "metadata": {"source": "Mapping Relationships Between Documentary Standards, Regulations, Frameworks, and Guidelines_ Developing Cybersecurity and Privacy Concept Mappings", "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 Guidelines on Security and Privacy in Public Cloud Computing:\n\n| Executive Summary.................................................................................................................vi | Executive Summary.................................................................................................................vi | Executive Summary.................................................................................................................vi |\n|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction....................................................................................................................... 1 | 1. Introduction....................................................................................................................... 1 | 1. Introduction....................................................................................................................... 1 |\n| 1.1 | Authority | ..................................................................................................................... 1 |\n| 1.2 | Purpose and Scope...................................................................................................."}], "metadata": {"source": "Guidelines on Security and Privacy in Public Cloud Computing", "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 De-Identifying Government Datasets_ Techniques and Governance:\n\n| 4. Technical Steps for Data De-Identifcation | 4. Technical Steps for Data De-Identifcation | . . . . . . . . . . . . . . . . . . . . . . | 46 |\n|------------------------------------------------|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|------|\n| 4.1. | Determine the Privacy, Data Usability, and Access Objectives . . . . . . | . . | 46 |\n| 4.2. | Conducting a Data Survey . . . . . . . . . . . . . | . . . . . . . . . . . . . . . | 47 |\n| 4.3. | De-Identifcation by Removing Identifers and Transforming Quasi-Identifers | De-Identifcation by Removing Identifers and Transforming Quasi-Identifers | 49 |\n| | 4.3.1. | Removing or Transforming of Direct Identifers . . . . . . . . . . . . | 51 |\n| | 4.3.2. | Special Security Note Regarding the Encryption or Hashing of Di- rect Identifers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | 52 |\n| | 4.3.3. | De-Identifying Numeric Quasi-Identifers . . . . . . . . . . . . . . . . | 53 |\n| | 4.3.4. | De-Identifying Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . | 54 |\n| | 4.3.5. | De-Identifying Geographical Locations and Geolocation Data . . . | 55 |\n| | 4.3.6. | De-Identifying Genomic Information . . . . . . . . . . . . . . . . . . | 56 |\n| | 4.3.7. | De-Identifying Text Narratives and Qualitative Information . . . . . | 57 |\n| | 4.3.8."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "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 Managing the Security of Information Exchanges provide? (Part 4)"}, {"role": "assistant", "content": ". However, it is recognized that the information being exchanged also requires the same or similar level of protection as it moves from one organization to another (protection commensurate with risk).\nThis publication focuses on managing the protection of the information being exchanged or accessed before, during, and after the exchange and provides guidance on identifying information exchanges, considerations for protecting exchanged information, and the agreement(s) needed to help manage the risk associated with exchanging information. This publication does not provide implementation guidance on any particular type of technology-based connection, information access, or exchange method. Organizations are expected to tailor the guidance to meet specific organizational needs and requirements regarding the information exchange. ## Keywords\n\nagreements; connection; information exchange; information exchange agreement; interconnection; interconnection security agreement; memoranda of agreement; memoranda of understanding; nondisclosure agreement; protection requirements; risk management; service level agreement; user agreement. ## Acknowledgments\n\nThe authors - Kelley Dempsey, Victoria Yan Pillitteri, and Andrew Regenscheid - wish to thank their colleagues who reviewed drafts of this publication and provided valuable input, including Joseph Boone, Joshua Finney, Stephen Ford, Greg Frassmann, Ann Galchutt, Jay Gazlay, Nedim Goren, Alan McClelland, Douglas Montgomery, Thomas Ritz, Scott Rose, John Simms, and Scott Spitnale . The authors also gratefully acknowledge Editorial Review Board reviewers Alan McClelland and Michael Bartock, the work of the original authors of SP 800-47, Tim Grance, Joan Hash, Steven Peck, Jonathan Smith, and Karen Korow-Diks; and the preliminary updates made by Michael Nieles."}], "metadata": {"source": "Managing the Security of Information Exchanges", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n- A method to identify opportunities for improving the current cybersecurity posture of the manufacturing system - An evaluation of their ability to operate the control environment at their acceptable risk level - A standardized approach to preparing the cybersecurity plan for ongoing assurance of the manufacturing system's security | Function Unique Identifier | Function | Category Unique Identifier | Category | |------------------------------|------------|------------------------------|--------------------------------------------------------| | ID | Identify | ID.AM | Asset Management | | ID | Identify | ID.BE | Business Environment | | ID | Identify | ID.GV | Governance | | ID | Identify | ID.RA | Risk Assessment | | ID | Identify | ID.RM | Risk Management Strategy | | ID | Identify | ID.SC | Supply Chain Management | | PR | Protect | PR.AC | Identity Management, Authentication and Access Control | | PR | Protect | PR.AT | Awareness and Training | | PR | Protect | PR.DS | Data Security | | PR | Protect | PR.IP | Information Protection Processes and Procedures | | PR | Protect | PR.MA | Maintenance | | PR | Protect | PR.PT | Protective Technology | | DE | Detect | DE.AE | Anomalies and"}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Foundations of a Security Policy for Use of the National Research and Educational Network:\n\nThe U.S. Government has since 1984 become increasingly aware of the essential role played by information technology in practically all areas of research and development. Bell reports [BELL88], the U.S. Congress requested in 1986 that OSTP study the potential development of a communications network for research computers, including supercomputers at universities and Federal research facilities. In recent years, a number of agencies, committees, and councils have been instrumental in the advising the government in its planning for HPCC and national networking -"}], "metadata": {"source": "Foundations of a Security Policy for Use of the National Research and Educational Network", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Considerations for Voice Over IP 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. VOIP is still an emerging technology, so it is difficult to develop a complete picture of what a mature worldwide VOIP network will one day look like. As the emergence of SIP has shown, new technologies and new protocol designs have the ability to radically change VOIP. Although there are currently many different architectures and protocols to choose from, eventually a true standard will emerge. Unless a widely used open standard emerges, solutions will be likely to include a number of proprietary elements, which can limit an enterprise's future choices. The most widely used of the competing standards are SIP and H.323. Some observers believe that SIP will become dominant. Major vendors are investing an increasing portion of their development effort into SIP products. An extension of SIP, the SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE) standard, is being incorporated into products that support Instant Messaging. Until a truly dominant standard emerges, organizations moving to VOIP should consider gateways and other network elements that support both H.323 and SIP. Such a strategy helps to ensure a stable and robust VOIP network in the years that come, no matter which protocol prevails."}], "metadata": {"source": "Security Considerations for Voice Over IP Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.7 (NIST 3.6.7)?"}, {"role": "assistant", "content": "According to Derived PIV Application and Data Model Test Guidelines:\n\n3.6.7)."}], "metadata": {"source": "Derived PIV Application and Data Model Test Guidelines", "cmmc_level": "all", "nist_control": "3.6.7", "cmmc_practice_id": "IR.L2-3.6.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n- identify known and anticipated threats to the satellite ground segment and supporting infrastructure;\n- protect the systems that the ground segment relies on through policy, training, resilience, and access control;\n- detect a loss of ground segments' confidentiality, integrity, or availability;\n- respond to confidentiality breaches of Telemetry, Tracking, and Command (TT&C) and a manipulation or loss of satellite commands or telemetry in a timely, effective, and resilient manner; and\n- recover from anomalies in a timely, effective, and resilient manner."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Representation of PIV Chain-of-Trust for Import and Export provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-156\n\n## Representation of PIV Chain-of-Trust for Import and Export\n\nHildegard Ferraiolo Ramaswamy Chandramouli Ketan Mehta Jason Mohler Stephen Skordinski Steven Brady\n\nThis publication is available free of charge from:\n\nhttp://dx.doi.org/10.6028/NIST.SP.800-156\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-156\n\n## Representation of PIV Chain-of-Trust for Import and Export\n\nHildegard Ferraiolo Ramaswamy Chandramouli Ketan Mehta Computer Security Division Information Technology Laboratory\n\nJason Mohler Stephen Skordinski Steven Brady Electrosoft Services Inc. Reston, VA\n\nThis publication is available free of charge from:\n\nhttp://dx.doi.org/10.6028/NIST.SP.800-156\n\nMay 2016\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director\n\n## Authority\n\nThis publication has been developed by NIST to further its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3541 et seq. , Public Law 113283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "Representation of PIV Chain-of-Trust for Import and Export", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A. C-SCRM Security Controls............................................................................................... | 63 |\n| A.1.1."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\n- „ The organization is limited to the VPN functionality offered by its firewall vendor. It does not have the option of using a VPN appliance because appliances are separate hardware devices. - „ The firewall is directly accessible by external users on TCP port 443. This increases the likelihood of a vulnerability on the firewall that can be exploited via these ports. - „ The firewall must be augmented by SSL VPN functionality. This additional code could introduce potential vulnerabilities to the firewall. the VPN tunnel. It sends all traffic not destined for the internal (protected) network through its standard network connection and only sends traffic destined for the internal network through the VPN tunnel. Split tunneling offers the advantages of efficiency and bandwidth conservation, as traffic destined for the Internet does not have to be sent first to the VPN device. On the other hand, split tunneling also creates a potential security vulnerability. If an attacker from the Internet compromises the client machine, then this attacker can use the split tunnel to also access the organization's internal network. The organization must weigh the advantages and disadvantages of split tunneling before deciding to implement it. - „ Security of the Implementation. Parts of the SSL VPN's implementation, such as the SSL code or the firewall code, may contain vulnerabilities that attackers could exploit. Organizations with high security requirements may want to perform extensive vulnerability assessments against the SSL VPN components. At a minimum, the testers should update the SSL VPN components with the latest patches and configure the components following sound security practices. If the device supports features to protect against cross-site scripting, Structured Query Language (SQL) injection, and buffer overflow attacks, then these features should be enabled. - „ Endpoint Security."}], "metadata": {"source": "Guide to SSL VPNs", "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 Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\n1. IR 8259A, IoT Device Cybersecurity Core Baseline [1], defines a baseline of six technical cybersecurity capabilities that IoT devices provide through their own technical means (i.e., device hardware and software).\n2. IR 8259B, IoT Non-Technical Supporting Capability Core Baseline [2], defines a baseline of four non-technical cybersecurity capabilities that a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device (e.g., providing information about software updates, instructions for configuration settings, and supply chain information).\n\nDevice cybersecurity capabilities are cybersecurity features or functions that IoT devices provide through their own technical means (i.e., device hardware and software). Non-technical supporting capabilities are actions that a manufacturer or third-party organization performs in support of the cybersecurity of an IoT device (e.g., providing information about software updates, instructions for configuration settings, and supply chain information). Used together, device cybersecurity capabilities and non-technical supporting capabilities can help mitigate cybersecurity risks related to the use of IoT devices while assisting customers in achieving their goals."}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Small Business Information Security_ The Fundamentals provide? (Part 4)"}, {"role": "assistant", "content": ".................................... PURPOSE ...........................................................................................................................................................\n| 1 1 |\n|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|\n| 1 | BACKGROUND: WHAT IS INFORMATION SECURITY AND CYBERSECURITY?.............................................. | BACKGROUND: WHAT IS INFORMATION SECURITY AND CYBERSECURITY?.............................................. | 2 |\n| | 1.1 | WHY SMALL BUSINESSES?"}], "metadata": {"source": "Small Business Information Security_ The Fundamentals", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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.7 (NIST 3.3.7)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n3.3.7. 3.3.7. 3.3.7."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "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 is CMMC practice AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities:\n\n3.1.1 Security Awareness Roles and Percentage of Time... 3.1.1 Security Awareness Roles and Percentage of Time... 3.1.1 Security Awareness Roles and Percentage of Time..."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Secure Web Services:\n\n| | 3.5.4 | XACML.......................................................................................................3-25 | | |---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| | | 3.5.5 | Role of XML Schema in Implementing Access Control..............................3-28 | | | | 3.5.6 | Use of Specialized Security Metadata for Access Control | .........................3-29 | | 3.6 | Confidentiality and Integrity of Service to Service Interchanges............................3-30 | Confidentiality and Integrity of Service to Service Interchanges............................3-30 | | | | 3.6.1 | Transport Layer Confidentiality and Integrity: HTTPS................................3-30 | | | | 3.6.2 | XML Confidentiality and Integrity................................................................3-30 | | | | 3.6.3 | WS-Security for SOAP Confidentiality and Integrity | ...................................3-31 | | | 3.6.4 | Role of XML Gateways in Integrity Protection............................................3-32 | | | 3.7 | Accountability End-to-End throughout a Service Chain.........................................3-33 | Accountability End-to-End throughout a Service Chain.........................................3-33 | | | | 3.7.1 Audit in the SOA Environment....................................................................3-34 | 3.7.1 Audit in the SOA Environment....................................................................3-34 | | | | 3.7.2 | Non-Repudiation of Web Service Transactions..........................................3-34 | | | 3.8 | Availability of Web Services...................................................................................3-35 | Availability of Web Services...................................................................................3-35 | | | | 3.8.1 | Failover.......................................................................................................3-36 | | | | 3.8.2 | Quality of Service | .......................................................................................3-36 | | | 3.8.3 | Reliable Messaging | ....................................................................................3-37 | | | 3.8.4 | Handling Service Deadlock"}], "metadata": {"source": "Guide to Secure Web Services", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Recommended Criteria for Cybersecurity Labeling of Consumer Software:\n\n- Supplier's declaration of conformity (self-attestation) where the declaration of conformity is performed by the organization that provides the software. This is a self-attestation against a defined set of criteria.\n- Third-party testing or inspection where there is determination or examination of the consumer software based on defined criteria.\n- Third-party certification of the consumer software."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling of Consumer Software", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective:\n\nIdentity and Access Management and related standards enable the use of secure, interoperable digital identities and attributes of entities to be used across security domains and organizational boundaries. Examples of entities include people, places, organizations, hardware devices, software applications, information artifacts, and physical items. Standards for identity and access management support identification, authentication, authorization, privilege assignment, and audit to ensure that entities have appropriate access to information, services, and assets. In addition, many identity and access management standards include privacy features to maintain anonymity, unlinkability, untraceability, ensure data minimization, and require explicit user consent when attribute information may be shared among entities.\n\nCSA: The Cloud Security Alliance (CSA) is dedicated to defining and raising awareness of best practices and the development of industry standards to help ensure a secure cloud computing environment. Present cybersecurity related standards include: the Cloud Control Matrix (CCM), a security control framework specifically dedicated to Cloud Computing; Consensus Assessment Initiative Questionnaire (CAIQ), a due diligence framework to guide organizations in the assessment of the CCM controls implementation; CloudAudit, a common interface and namespace that allows enterprises to streamline their audit processes; and Privacy Level Agreement (PLA), a guidance to achieve a baseline compliance with mandatory personal data protection legislation across the European Union (EU).\n\nSecurity 28 may also be defined as the preservation of confidentiality, integrity and availability of information. NOTE In addition, other properties, such as authenticity, accountability, nonrepudiation, and reliability can also be relevant."}], "metadata": {"source": "Supplemental Information for the Interagency Report on Strategic U.S. Government Engagement in International Standardization to Achieve U.S. Objective", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\n| C.3.3 Human Resource Management ........................................................................................74 | | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------| | C.3.3.1 HR Strategy Information Type..................................................................................74 | | | C.3.3.2 Staff Acquisition Information Type..........................................................................75 | | | C.3.3.3 Organization &Position Management Information Type.........................................76 | | | C.3.3.4 Compensation Management Information Type.........................................................77 | | | C.3.3.5 Benefits Management Information Type | ..................................................................78 | | C.3.3.6 Employee Performance Management Information Type..........................................79 | | | C.3.3.7 Employee Relations Information Type | .....................................................................81 | | C.3.3.8 Labor Relations Information Type............................................................................82 | | | C.3.3.9 Separation Management Information Type...............................................................83 | | | C.3.3.10 Human Resources Development Information Type................................................84 | | | C.3.4 Supply Chain Management..............................................................................................85 | | | C.3.4.1 Goods Acquisition Information Type | .......................................................................85 | | C.3.4.2 Inventory Control Information Type.........................................................................87 | | | C.3.4.3 Logistics Management Information Type.................................................................88 | | | C.3.4.4 Services Acquisition Information Type | ....................................................................89 | | C.3.5 Information and Technology Management......................................................................91 | | | C.3.5.1 System Development Information Type | ...................................................................91 | | C.3.5.2 Lifecycle/Change Management Information Type | ...................................................92 | | C.3.5.3 System Maintenance Information Type....................................................................93 | | | C.3.5.4 IT Infrastructure Maintenance Information Type | .....................................................94 | | C.3.5.5 Information Security Information Type....................................................................96 | | | C.3.5.6 Record Retention Information Type..........................................................................97 | | | C.3.5.7 Information Management Information"}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "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 Computer Security Division 2007 Annual Report provide? (Part 4)"}, {"role": "assistant", "content": "to meet new and revised requirements for federal agency use of cryptographic systems, and to address technological and economic changes that have occurred since the issuance of FIPS 140-2 in 2001.\nOpportunities were presented during FY 2007 for CSD to apply its security research to national priorities and internal NIST initiatives. The CSD significantly expanded its support for two key national initiatives, electronic voting and health information technology, by researching the security requirements of those areas and applying the results of that research, along with current technologies, in furtherance of the stated goals of those initiatives. CSD also worked closely with the NIST ITL management team to integrate security projects into newly formed research programs. These programs, which include Cyber Security, Pervasive Information Technologies, Trustworthy Networking, and Trustworthy Software, are designed to organize and build ITL core competencies in the most efficient manner, and to maximize the use of ITL resources to address emerging information technology challenges. These are just some of the highlights of the CSD program during FY 2007. You may obtain more information about CSD's program at http://csrc.nist.gov or by contacting any of the CSD experts noted in this report. If interested in participating in any CSD challenges -whether current or future - please contact any of the listed CSD experts."}], "metadata": {"source": "Computer Security Division 2007 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Maintenance?"}, {"role": "assistant", "content": "According to Fiscal Year 2023 Cybersecurity and Privacy Annual Report:\n\n- NIST continued the Journey to Cybersecurity Framework (CSF) 2.0 by releasing a CSF 2.0 Concept Paper, publishing a discussion draft of the CSF 2.0 Core, and issuing a draft CSF 2.0 with Core Implementation examples. Additionally, NIST published an analysis of comments received on each draft and hosted two hybrid workshops (1 st workshop & 2 nd workshop). - NIST continued to lead and support community engagement on cybersecurity supply chain risk management through the Software and Supply Chain Assurance (SSCA) Forum, support the Federal Acquisition Security Council, and refine supply-chain guidance in SP 800-161 Revision 1, Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations . - NIST issued a working draft of the SP 800-55 Rev. 2, Performance Measurement Guide for Information Security for community discussion and feedback and hosted a cybersecurity measurement workshop on the current state of cybersecurity performance measurement, needs, and path forward. - NIST initiated updates to the Protecting Controlled Unclassified Information (CUI) Series, issued a pre-call for comment, released an initial public draft of SP 800-171r3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, and hosted a webinar to provide an overview of the draft. - NIST launched the Cybersecurity & Privacy Reference Tool (CPRT) - an online application that provides NIST guidance and frameworks in a consistent format for reference data and allows users to understand the relationships between NIST resources. - NIST continued the development of the Open Security Controls Assessment Language (OSCAL) - a set of eXtensible Markup Language (XML), JavaScript Object Notation (JSON), and Ain't Mark-up Language (YAML) formats that provide machine-readable representations of security and privacy information relative to the implementation, assessment, and continuous monitoring of systems."}], "metadata": {"source": "Fiscal Year 2023 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface:\n\nFIPS 201 defines the requirements and characteristics of government-wide interoperable identity credentials. It specifies that these identity credentials must be stored on a smart card and that additional common identity credentials, known as derived PIV credentials, may be issued by a federal department or agency and used when a PIV Card is not practical. This document contains the technical specifications to interface with the smart card to retrieve and use the PIV identity credentials. The specifications reflect the design goals of interoperability and PIV Card functions. The goals are addressed by specifying a PIV data model, card edge interface, and application programming interface. Moreover, this document enumerates requirements for the options and branches in international integrated circuit card standards [ISO7816]. The specifications go further by constraining interpretations of the normative standards to ease implementation, facilitate interoperability, and ensure performance in a manner tailored for PIV applications. | 1. Introduction...................................................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. Overview: Concepts and Constructs................................................................................................3 |\n| 2.3.1. Default Selected Card Application................................................................................................4 |\n| 2.4.1. Access Control Rule......................................................................................................................5 |\n| 2.4.2. Security Status..............................................................................................................................5 |\n| 2.4.3."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\nEXECUTIVE SUMMARY .................................................................................................................. IX\nContent of the Report ............................................................................................................................ xi\n CHAPTER 1 DOCUMENT DEVELOPMENT STRATEGY ...................................................................1\n1.1 Cybersecurity and the Electric Sector ............................................................................................ 4\n1.2 Scope and Definitions .................................................................................................................... 5\n1.3 Smart Grid Cybersecurity Document Development Strategy ........................................................ 6\n1.4 Combined Cyber-Physical Attacks .............................................................................................. 12\n CHAPTER 2 LOGICAL ARCHITECTURE AND INTERFACES OF THE SMART GRID ......................14\n2.1 The Seven Domains to the Logical Reference Model ................................................................. 15\n2.2 Logical Security Architecture Overview ..................................................................................... 24\n2.3 Logical Interface Categories ........................................................................................................ 28\n CHAPTER 3 HIGH-LEVEL SECURITY REQUIREMENTS ...............................................................75\n3.1 Cybersecurity Objectives ............................................................................................................. 75\n3.2 Confidentiality, Integrity, and Availability Impact Levels .......................................................... 76\nImpact Levels for the CI&A Categories ......................................................................................"}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "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 3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report:\n\nThe panel identified software supply chain security as both a current and future challenge, especially in HPC, where code provenance is largely unknown and users compile their own code. Asked how they might redesign HPC systems to be more secure, one panelist emphasized the power of virtualization, containers, and the ability to limit the attack surface. The panel discussed the relative merits, performance, and obstacles to such a pure container-based approach.\n\n- Composable/disaggregated systems (CXL) and their implications on architectures\n- Multi-tenancy: Exploring how to efficiently share resources among multiple users or applications\n- Supply chain security: Ensuring the integrity and security of hardware components throughout the supply chain\n- Real-time authorization of components: Enabling the verification and authorization of components in real time\n- Transition from Trusted Platform Module 2.0 (TPM2) to Virtual TPM (VTPM): Evaluating the benefits and challenges of transitioning from TPM2 to Virtual TPM\n- SmartNICs and the software executed on them: Understanding the role of SmartNICs and the software running on them for enhancing system performance and security\n- Software-defined networks (SDNs): Leveraging SDNs to enable more flexible and efficient network management\n\n- Transition to RMF and the subsequent move to the Cybersecurity Maturity Model Certification (CMMC) in the coming decade\n- Zero trust approach and its relevance to HPC systems: Implementing a zero trust architecture that assumes no inherent trust in the system components and networks\n- Supply chain management: Developing strategies to mitigate the risks associated with the supply chain, including hardware and software components"}], "metadata": {"source": "3rd High-Performance Computing Security Workshop_ Joint NIST-NSF Workshop Report", "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 System and Information Integrity?"}, {"role": "assistant", "content": "According to Computer Security Division 2010 Annual Report:\n\nWe also invite public and private organizations to submit their in­ formation security practices to be considered for inclusion on the website. Policies and procedures may be submitted to us in any area of information security, such as accreditation, audit trails, au­ thorization of processing, budget planning and justification, cer­ tification, contingency planning, data integrity, disaster planning, documentation, hardware and system maintenance, identification and authentication, incident handling and response, life cycle, network security, personnel security, physical and environmental protection, production input/output controls, security policy, pro­ gram management, review of security controls, risk management, security awareness training and education (including specific training course and awareness materials), and security planning. Health information technology (HIT) makes it possible for health­ care providers to better manage patient care through secure use and sharing of health information, leading to improvements in healthcare quality, reduced medical errors, increased efficiencies in care delivery and administration, and improved population health. Central to reaching these goals is the assurance of the confidentiality, integrity, and availability of health information. The CSD works actively with government, industry, academia, and others to provide security tools, technologies, and methodologies that provide for the security and privacy of health information. As part of that work, CSD participates with, and provides technical advice to, agencies, organizations, and standards committees and panels that are shaping the HIT arena, including the Department of Health and Human Services' (HHS), Office of the National Coor­ dinator for Health IT (ONC), and Office for Civil Rights (OCR)."}], "metadata": {"source": "Computer Security Division 2010 Annual Report", "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 Ordered t-way Combinations for Testing State-based Systems:\n\nement Concepts and Applications\", 2nd Intl Workshop on Combinatorial Testing , Luxembourg, IWCT2013, IEEE, Mar. 2013. - [27] Zamli KZ, Othman RR, Zabil MH. On sequence based interaction testing.\nIn2011 IEEE Symposium on Computers & Informatics 2011 Mar 20 (pp. 662-667). IEEE. - [28] Kuhn DR, Higdon JM, Lawrence JF, Kacker RN, Lei Y. Efficient methods for interoperability testing using event sequences. FLIGHT TEST SQUADRON (46TH) EGLIN AFB FL; 2012 Aug 1. - [29] Yilmaz C, Fouche S, Cohen MB, Porter A, Demiroz G, Koc U. Moving forward with combinatorial interaction testing. Computer. 2013 Dec 11;47(2):37-45. - [30] Garn B, Simos DE, Zauner S, Kuhn R, Kacker R. Browser fingerprinting using combinatorial sequence testing. In Proceedings of the 6th Annual Symposium on Hot Topics in the Science of Security 2019 Apr 1 (pp. 1-9). - [31] Ozcan M. An Industrial Study on Applications of Combinatorial Testing in Modern Web Development. In2019 IEEE International Conference on Software Testing, Verification and Validation Workshops (ICSTW) 2019 Apr 22 (pp. 210-213). - [32] Ratliff, Z. B. (2018). Black-box Testing Mobile Applications Using Sequence Covering Arrays. undergraduate thesis, Texas A&M University. - [33] Ratliff ZB, Kuhn DR, Ragsdale DJ. Detecting Vulnerabilities in Android Applications using Event Sequences. In2019 IEEE 19th International Conference on Software Quality, Reliability and Security (QRS) 2019 Jul 22 (pp. 159-166). IEEE. - [34] Elks DC, Deloglos C, Jayakumar A, Tantawy DA, Hite R, Gautham S. Realization Of An Automated T-Way Combinatorial Testing Approach For A Software Based Embedded Digital Device. Idaho National Lab.(INL), Idaho Falls, ID (United States); 2019 Jun 17. - [35] Becci G, Dhadyalla G, Mouzakitis A, Marco J, Moore AD. Robustness testing of real-time automotive systems using sequence covering arrays. SAE International Journal of"}], "metadata": {"source": "Ordered t-way Combinations for Testing State-based Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommendation for Applications Using Approved Hash Algorithms provide? (Part 5)"}, {"role": "assistant", "content": "|\n| 5 | Hash function Usage..........................................................................\n| Hash function Usage.......................................................................... | 9 |\n| | 5.1 | Truncated Message Digest........................................................................ | 9 |\n| | 5.2 | Digital Signatures.................................................................................... | 10 |\n| | | 5.2.1 Full-length Message | Digests..................................................."}], "metadata": {"source": "Recommendation for Applications Using Approved Hash Algorithms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Security Considerations for Remote Electronic UOCAVA Voting:\n\ns, monitor how voters vote, and use the election official's credential to gain and expand access to damage the voting system, change election results, and harm the credibility of the election results.\nAlthough the election official is not actively participating in attacking the remote electronic voting system, the console they use to interact with the voting system poses a threat that appears to be from an election official."}], "metadata": {"source": "Security Considerations for Remote Electronic UOCAVA Voting", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Understanding Stablecoin Technology and Related Security Considerations:\n\nThis configuration is the most common (and is exclusively the case in the top 20 studied stablecoins)."}], "metadata": {"source": "Understanding Stablecoin Technology and Related Security Considerations", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products:\n\ne not met by IoT product components and why (e.g., the capability is not needed based on risk assessment). - d. Product design and support considerations related to the IoT product, for example :\n- i.\nAll hardware and software components, from all sources (e.g., open source, propriety third-party, internally developed) used to create the IoT product (i.e., used to create each product component). - ii. IoT platform used in the development and operation of the IoT product, its product components, including related documentation. - iii. Protection of software and hardware elements implemented to create the IoT product and its product components (e.g., secure boot, hardware root of trust, and secure enclave)."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Access Control?"}, {"role": "assistant", "content": "According to Computer Security Division 2010 Annual Report:\n\nSecurity and Health Information Technology National Initiative for Cybersecurity Education (NICE) | 9 14 | Access Control and Privilege Management Research Security for Grid and Pervasive Systems Security Ontologies: Modeling Quantitative Risk Analysis Enterprise Systems Protecting | 31 | | | 13 | NIST Cloud Computing Project Policy Machine | | | Security Practices and Policies Small and Medium Size Business Outreach | 12 12 | Automated Combinatorial Testing for Software Conformance Verification for Access Control Policies Forensics forWeb Services Mobile Handheld Device Security and Forensics | 31 32 33 33 | | | 11 11 | | | | | | | 34 | | | | | 35 35 36 | | Smart Grid Cyber Security | | | | | | | Virtualization Technologies Cloud Computing andVirtualization Laboratory | 36 36 36 | | Supply Chain Risk Management | 15 | | | | Cryptographic Validation Programs and Laboratory | 15 | Access Control and Identitiy Management in Virtualized Systems | 37 37 38 38 | | Accreditation Cryptographic ModuleValidation Program and Cryptographic | 16 16 17 18 | Security Content Automation Protocol (SCAP) National Vulnerability Database National Checklist Program Security Content Automation Protocol Validation Program |"}], "metadata": {"source": "Computer Security Division 2010 Annual Report", "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 System and Information Integrity?"}, {"role": "assistant", "content": "According to Computer Security Division 2014 Annual Report:\n\nanonymity and credentials, and specific privacy-enhancing technologies. In the past year, NIST continued to support the EAC in finalizing changes to the Voluntary Voting System Guidelines (VVSG) 1.1.\nThe security guidelines were updated in FY 2012 to improve the auditability of voting systems, to provide greater software integrity protections, to expand and improve access-control requirements, and to help ensure"}], "metadata": {"source": "Computer Security Division 2014 Annual Report", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Guidelines on Securing Public Web Servers:\n\n| Introduction ......................................................................................................................1-1 | | | | | 1.1 | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope .................................................................................................1-1 | | | | 1.3 | Audience and Assumptions .....................................................................................1-2 | | | | 1.4 Document | Structure.................................................................................................1-2 | | | 2."}], "metadata": {"source": "Guidelines on Securing Public Web Servers", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog:\n\n| 29 | | (AEI) Access to Event Information | ................................................................29 | | (EIM) Event Identification & Monitoring | .........................................................29 | | (EVR) Event Response.................................................................................30 | | | (LCT) Logging Capture & Trigger Support | ....................................................31 | | (RDL) Support of Required Data Logging | .....................................................31 | | (LSR) Audit Log Storage & Retention ...........................................................32 | | | (SRT) Support for Reliable Time...................................................................32 | | | (AUP) Audit Support & Protection .................................................................33 | | | (AWR) State Awareness Support..................................................................34 | | | DS - DEVICE SECURITY ....................................................................................."}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\n3.2.3 OIML D31:2019 6."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "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 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 does CMMC Level 2 require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Personal Identity Verification (PIV) of Federal Employees and Contractors:\n\nIn the case of deprecated features on PIV Cards such as the magnetic stripe (Section 4.1.4.4), existing PIV Card stock with deprecated features remains valid. However, future PIV Card stock acquisitions SHOULD exclude the deprecated features.\n\nThe card issuer SHALL maintain the enrollment record for each issued PIV Card. These enrollment records are created and maintained through the methods of contemporaneous acquisition at each step of the PIV issuance process-typically including identity proofing, registration, and biometric enrollment.\n\n- A log of activities that documents who took the action, what action was taken, when and where the action took place, and what data was collected.\n- An enrollment data record that contains the most recent collection of each of the biometric data collected. The enrollment data record describes the circumstances of biometric acquisition including the name and role of the acquiring agent, the office and organization, time, place, and acquisition method. The enrollment data record MAY also document unavailable biometric data or failed attempts to collect"}], "metadata": {"source": "Personal Identity Verification (PIV) of Federal Employees and Contractors", "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 guidance does Module-Lattice-Based Key-Encapsulation Mechanism Standard provide?"}, {"role": "assistant", "content": "\n\n## FIPS 203\n\n## Federal Information Processing Standards Publication\n\n## Module-Lattice-Based Key-Encapsulation Mechanism Standard\n\nCategory:\n\nComputer Security\n\nSubcategory:\n\nCryptography\n\nInformation Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8900\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.FIPS.203\n\nPublished August 13, 2024\n\n\n\nCommerce\n\nU.S. Department of 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\n## Foreword\n\nThe Federal Information Processing Standards (FIPS) Publication Series of the National Institute of Standards and Technology is the official series of publications relating to standards and guidelines developed under 15 U.S.C. 278g-3, and issued by the Secretary of Commerce under 40 U.S.C. 11331. Comments concerning this Federal Information Processing Standard publication are welcomed and should be submitted using the contact information in the 'Inquiries and Comments' clause of the announcement section. Kevin M. Stine, Director Information Technology Laboratory\n\n## Abstract\n\nA key-encapsulation mechanism (KEM) is a set of algorithms that, under certain conditions, can be used by two parties to establish a shared secret key over a public channel. A shared secret key that is securely established using a KEM can then be used with symmetric-key cryptographic algorithms to perform basic tasks in secure communications, such as encryption and authentication. This standard specifies a key-encapsulation mechanism called ML-KEM. The security of ML-KEM is related to the computational difficulty of the Module Learning with Errors problem. At present, ML-KEM is believed to be secure, even against adversaries who possess a quantum computer. This standard specifies three parameter sets for ML-KEM."}], "metadata": {"source": "Module-Lattice-Based Key-Encapsulation Mechanism Standard", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to 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 require for Access Control?"}, {"role": "assistant", "content": "According to Recommendation for Random Bit Generator (RBG) Constructions:\n\n| 1. Introduction and Purpose...............................................................................................................1 |\n|---------------------------------------------------------------------------------------------------------------------------------------------------|\n| 2. General Information.......................................................................................................................3 |\n| 2.4.1. DRBG Instantiations......................................................................................................................8 |\n| 2.4.2. Reseeding, Prediction Resistance, and Compromise Recovery ...................................................9 |\n| 2.8.1. DRBG Functions..........................................................................................................................15 |\n| 2.8.1.1. DRBG Instantiation ...............................................................................................................15 |\n| 2.8.1.2. DRBG Generation Request....................................................................................................17 |\n| 2.8.1.3. DRBG Reseed ........................................................................................................................19 |\n| 2.8.1.4. Get_randomness_source_input Call ....................................................................................20 |\n| 2.8.2. Interfacing With Entropy Sources ..............................................................................................20 |\n| 2.8.3. Interfacing With an RBG3 Construction .....................................................................................21 |\n| 2.8.3.1. Instantiating a DRBG Within an RBG3 Construction.............................................................21 |\n| 2.8.3.2."}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1:\n\n3.2.3. 3.2.3. 3.2.3, A."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.1", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Guidelines for Evaluating Differential Privacy Guarantees:\n\n3.3.1. 3.3.1. 3.3.1."}], "metadata": {"source": "Guidelines for Evaluating Differential Privacy Guarantees", "cmmc_level": "all", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations:\n\nspecifically authorized to access the information being protected. In asymmetric key cryptography, only one key in the key pair, the private key, must be kept secret; the other key can be made public.\nSymmetric key cryptography is most often used to protect the confidentiality of information or to authenticate the integrity of that information. Asymmetric key cryptography is commonly used to protect the integrity and authenticity of information and to establish symmetric keys."}], "metadata": {"source": "Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers:\n\n-  Configuration files that automatically set or verify various security-related settings (e.g., executables, security templates that modify settings, Security Content Automation Protocol (SCAP) XML (Extensible Markup Language) files, and scripts). 4\n-  Documentation (e.g., text file) that guides the checklist user to manually configure an IT product\n-  Documents that explain the recommended methods to securely install and configure a device\n-  Policy and programmatic documents that set forth guidelines for such things as auditing, authentication mechanisms (e.g., passwords), and perimeter security.\n\nThe Managed environment, also referred to as Enterprise , comprises centrally managed IT products, everything ranging from servers and printers to desktops, laptops, smartphones, and tablets. Managed checklists are intended for advanced end users and system administrators. The managed nature of typical Managed environments gives administrators centralized control over various settings on devices. Authentication, account, and policy management can also be administered centrally to maintain a consistent security posture across an organization."}], "metadata": {"source": "National Checklist Program for IT Products_ Guidelines for Checklist Users and Developers", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-73pt1-5\n\n## Interfaces for Personal Identity Verification\n\nPart 1 PIV Card Application Namespace, Data Model, and Representation\n\nHildegard Ferraiolo Ketan Mehta Salvatore Francomacaro Ramaswamy Chandramouli Sarbari Gupta\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-73pt1-5\n\n\n\n## NIST Special Publication 800 NIST SP 800-73pt1-5\n\n## Interfaces for Personal Identity Verification\n\nPart 1 -PIV Card Application Namespace, Data Model, and Representation\n\nHildegard Ferraiolo Ketan Mehta Salvatore Francomacaro Ramaswamy Chandramouli Computer Security Division Information Technology Laboratory\n\nSarbari Gupta\n\nElectrosoft Services, Inc. This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-73pt1-5\n\nJuly 2024\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology Laurie E. Locascio, NIST Director and Under Secretary of Commerce for Standards and Technology\n\nCertain 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": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\n## Secure Software Development Framework (SSDF) Version 1.1:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Framework Version 1.1 Manufacturing Profile provide? (Part 5)"}, {"role": "assistant", "content": "ce of the manufacturing system's security\n\nThe Profile is built around the primary functional areas of the Cybersecurity Framework which enumerate the most basic functions of cybersecurity activities.\nThe five primary functional areas are: Identify, Protect, Detect, Respond, and Recover. These primary functional areas comprise a starting point from which to develop a manufacturer-specific or sector-specific Profile at the defined risk levels of Low, Moderate and High. This Manufacturing 'Target' Profile focuses on desired cybersecurity outcomes and can be used as a roadmap to identify opportunities for improving the current cybersecurity posture of the manufacturing system. The Manufacturing Profile provides a prioritization of security activities to meet specific business/mission goals. Relevant and actionable security practices that can be implemented to support key business/mission goals are then identified. This Manufacturing Profile provides a voluntary, risk-based approach for managing cybersecurity activities and reducing cyber risk to manufacturing systems. The Manufacturing Profile is meant to enhance but not replace current cybersecurity standards and industry guidelines that the manufacturer is embracing. ## Table of Contents\n\n| Executive Summary......................................................................................................v | Executive Summary......................................................................................................v |\n|----------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\n3.3.5 | Encryption and Integrity Protection... 3.3.5 Encryption and Integrity Protection\n\nSSL VPNs use the underlying SSL protocol to protect the confidentiality of data using encryption and to provide data integrity (ensuring that the data has not been modified)."}], "metadata": {"source": "Guide to SSL VPNs", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Application Container Security Guide:\n\nアプリの脆弱性 | ..........................................................................................................................................18 | | 3.4.5 未承認コンテナ ..........................................................................................................................................18 | | | 3.5 ホスト OS のリスク ..........................................................................................................................................18 | | | 3.5.1 大きなアタックサーフェス | ........................................................................................................................18 |"}], "metadata": {"source": "Application Container Security Guide", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Personnel Security?"}, {"role": "assistant", "content": "According to Security Segmentation in a Small Manufacturing Environment:\n\non the network. | Security segmentation identifies assets and groups them into security zones, which can help with inventory management. Asset inventory is an intrinsic part of security segmentation.\n|\n| Poor visibility of assets and network traffic: without real-time visibility of assets and network traffic, it is difficult to detect new devices, nefarious activities, or a device going offline. | Security segmentation facilitates implementing network visibility tools through creation of security zones. Security zones break down assets into small groups, so it is easier to set up monitoring tools and analyze results. |\n| Lack of isolation: absence of isolation between different parts of the network enables an attacker to easily move from one system to another. | Grouping assets into security zones can make it easy to identify where to use isolation. |\n| Undefined separation of duties: without the capability to implement separation of duties, a single person may have the ability to change the way systems operate without any oversight or approval. This could allow an attacker who compromises that user's account to make changes without anyone else noticing. | Security segmentation can help clarify who should be able to make changes to systems and who should approve those changes, which can simplify implementation of role-based or rule-based authentication. |\n| Absence of least privilege: in a system that does not limit privileges, individuals may have the ability to perform actions they are not authorized to perform. Additionally, this means anyone with an account on a system can do whatever they want. This means an actor with access to one account can do more damage than if the account had limited privileges. | The application of security segmentation can make implementation of least privilege easier as each security zone has a well-defined function."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Computer Security Training & Awareness Course Compendium:\n\n| COURSE NAME | PAGE | |---------------------------------------------------------------------------|--------| | A FRAUD UPDATE: FORENSIC AND INVESTIGATIVE AUDITING | 24 | | A PRACTICAL APPROACH TO CERTIFYING A SYSTEM | 83 | | ADP SECURITY OFFICERS (ADPSO) CONCEPTS | 2 | | ADVANCED DATA COMM NETWORKS: SECURITY/AUDITABILITY | 55 | | ADVANCED EDP AUDITING - GBA 577 | 79 | | ADVANCED TECHNOLOGY CONFERENCE | 10 | | ADVANCED NETWORK SECURITY ARCHITECTURE | 75 | | AIS SECURITY STRATEGIES | 60 | | APPLICATION SECURITY REVIEWS | 30 | | ARCHITECTURE FOR SECURE SYSTEMS | 73 | | AUDIT SOFTWARE FOR THE 21ST CENTURY | 48 | | AUDIT AND SECURITY OF CLIENT/SERVER ARCHITECTURES | 24 | | AUDIT AND SECURITY OF RELATIONAL DATABASES AND APPLICATIONS | 57 | | AUDIT AND CONTROL OF END-USER COMPUTING (EUC) | 40 | | AUDIT AND CONTROL OF ELECTRONIC DATA INTERCHANGE | 39 | | AUDIT, CONTROL, AND SECURITY OF LAN AND MAINFRAME CONNECTIVITY | 31 | | AUDITING EDI APPLICATIONS | 47 | | AUDITING THE DATA CENTER FOR CONTROLS, EFFICIENCY, AND COST-EFFECTIVENESS | 68 | | AUDITING THE DATA CENTER (M2020) | 36 | | AUDITING FRAUD: PREVENT, DETECT, & CONTROL | 54 |"}], "metadata": {"source": "Computer Security Training & Awareness Course Compendium", "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 AU.L2-3.3.1 (NIST 3.3.1)?"}, {"role": "assistant", "content": "According to Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services:\n\n3.3.1 GPS SPS IANA TZDB ICAO 9849 1, 6. 3.3.1 IETFCMP 6 NIST SP 800-37 3 NIST SP 800-53 Rev."}], "metadata": {"source": "Foundational PNT Profile_ Applying the Cybersecurity Framework for the Responsible Use of Positioning, Navigation, and Timing (PNT) Services", "cmmc_level": "1", "nist_control": "3.3.1", "cmmc_practice_id": "AU.L2-3.3.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.2 (NIST 3.3.2)?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n3.3.2, 3. 3.3.2, 3. 3.3.2, 3."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "nist_control": "3.3.2", "cmmc_practice_id": "AU.L2-3.3.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security Division 2006 Annual Report:\n\n- Provide assistance in using NIST guides to comply with FISMA - Information Technology Laboratory (ITL) Computer Security Bulletin Understanding the New NIST Standards and Guidelines Required by FISMA: How Three Mandated Documents are Changing the Dynamic of Information Security for the Federal Government (issued November 2004). - Provide a specification for minimum security requirements for Federal information and information systems using a standardized, risk-based approach - Developed FIPS 200, Minimum Security Requirements for Federal Information and Information Systems (issued March 2006). - Define minimum information security requirements (management, operational, and technical security controls) for information and information systems in each such category - Developed SP 800-53, Recommended Security Controls for Federal Information Systems (revision 1 issued December 2006). - Identify methods for assessing effectiveness of security requirements - SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems (second public draft issued April 2006). - B ring the security planning process up to date with key standards and guidelines developed by NIST - SP 800-18 Revision 1, Guide for Developing Security Plans for Federal Information Systems (issued February 2006). - Provide assistance to Agencies and private sector - Conduct ongoing, substantial reimbursable and non-reimbursable assistance support, including many outreach efforts such as the Federal Information Systems Security Educators' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSM Forum), the Small Business Corner, and the Program Review for Information Security Management Assistance (PRISMA)."}], "metadata": {"source": "Computer Security Division 2006 Annual Report", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\n- Create clear standards and guidelines from a cybersecurity and privacy perspective for IoT device manufacturers and solution providers.\n- Certification and labeling programs are emerging for both devices and overall solutions.\n- Data standards, integration, and communication protocols can help facilitate ecosystem compatibility to ensure devices can communicate.\n- Dependable supply chains are important.\n- Clear and consistent standards increase device interoperability and decrease cost.\n- Providing direction on 'mandatory' requirements would benefit manufacturers.\n- Educating the workforce and/or future workforce for the digital transformation of the economy, such as developing training initiatives to increase skilled resources to implement and maintain IoT solutions.\n- Public and private partnerships strengthen IoT security by leveraging the strengths, knowledge, and resources from both industry and government.\n\nCommunication emerged as pivotal to both the pre-market and post-market stages across multiple discussions with participants regarding challenges, strategies, and roles. While some emphasized the limitations manufacturers face in direct communication with customers, especially for products sold through retailers or installed by integrators, others agreed that raising broader cybersecurity awareness is critical.\n\n- Education and awareness strategies targeting both consumer and workforce users that focuses on explaining IoT product behavior, mitigating anomalies, and practicing strong cybersecurity hygiene."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "cmmc_level": "1", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Identity Proofing and Enrollment:\n\n3.1.\n\n3.3.1. Privacy Risk Assessment . . . . . . . . . . . . . . . . . . . . . .\n\n4.3.1. Proofing Types . . . . . . . . . . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Security Considerations for Voice Over IP Systems:\n\n| Figure 1. Voice Data Processing in a VOIP System. ................................................................... | 15 |\n|-------------------------------------------------------------------------------------------------------------------------------------------|------|\n| Figure 2. Sample Latency Budget ................................................................................................ | 20 |\n| Figure 3. H.323 Architecture........................................................................................................ | 26 |\n| Figure 4. H.323 Call Setup Process.............................................................................................. | 27 |\n| Table 1: H235v2 Annex D - Baseline Security Profile ................................................................. | 29 |\n| Table 2: H235v2 Annex E - Signature Security Profile ............................................................... | 30 |\n| Table 3: H235v2 - Voice Encryption Option ................................................................................ | 31 |\n| Table 4: H235v2 Annex F - Hybrid Security Profile.................................................................... | 32 |\n| Table 5: H235v3 Annex D - Baseline Security Profile ................................................................. | 33 |\n| Figure 5. SIP Network Architecture............................................................................................. | 40 |\n| Figure 6. SIP Protocol .................................................................................................................. | 46 |\n| Figure 7: General Scenario for MGCP Usage............................................................................... | 48 |\n| Figure 8: General Scenario for MEGACO/H.248 Usage.............................................................. | 50 |\n| Figure 9."}], "metadata": {"source": "Security Considerations for Voice Over IP 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": "How does Security Requirements for Cryptographic Modules support CMMC certification?"}, {"role": "assistant", "content": "According to Security Requirements for Cryptographic Modules:\n\nas defined in 15 U.S.C. § 278g-3. This standard shall be used in designing and implementing cryptographic modules that federal departments and agencies operate or are operated for them under contract.\nThe standard provides four increasing, qualitative levels of security intended to cover a wide range of potential applications and environments. The security requirements cover areas related to the secure design, implementation and operation of a cryptographic module. These areas include cryptographic module specification; cryptographic module interfaces; roles, services, and authentication; software/firmware security; operating environment; physical security; non-invasive security; sensitive security parameter management; self-tests; life-cycle assurance; and mitigation of other attacks. Key words : computer security; telecommunication security; physical security; software security; cryptography; cryptographic modules; Federal Information Processing Standard (FIPS); ISO/IEC 19790; ISO/IEC 24759. ## Federal Information Processing Standards Publication 140-3\n\nMarch 22, 2019\n\n## Announcing the Standard for\n\n## SECURITY REQUIREMENTS FOR CRYPTOGRAPHIC MODULES\n\nFederal Information Processing Standards Publications (FIPS PUBS) are issued by the National Institute of Standards and Technology (NIST) after approval by the Secretary of Commerce pursuant 15 USC 278g-3. 1. Name of Standard. Security Requirements for Cryptographic Modules (FIPS PUB 140-3). 2. Category of Standard. Computer Security Standard, Cryptography. 3. Explanation. This standard specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system protecting sensitive but unclassified information (hereafter referred to as sensitive information). The standard provides four increasing, qualitative levels of security: Level 1, Level 2, Level 3, and Level 4."}], "metadata": {"source": "Security Requirements for Cryptographic Modules", "cmmc_level": "3", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\nAfter implementation measures are gathered, further analysis, not dissimilar to data normalization, is required before the results can be expressed to a non-technical audience. Successful effectiveness and efficiency assessments of individual phenomenon may require additional analysis using multiple measures. For example, when looking for 'delayed vulnerability remediations,' simply checking the mean time to incident response is unlikely to provide all of the information necessary to determine the causes of an issue."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "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 Guidelines on Electronic Mail Security:\n\n| | | | Summary..............................................................................................................ES-1 |\n|----|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|\n| 1."}], "metadata": {"source": "Guidelines on Electronic Mail 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 is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations:\n\n3.2.2 Key Management Planning Information Requirements________________________ | 34 |\n| 4 | Key Management Specification______________________________________39 | Key Management Specification______________________________________39 | |\n| | 4. 3.2.2 Key Management Planning Information Requirements\n\nThe level of key management planning detail required for cryptographic applications can be tailored, depending upon the scope and complexity of the application. 3.2.2."}], "metadata": {"source": "Recommendation for Key Management_ Part 2 – Best Practices for Key Management Organizations", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity of Genomic Data:\n\n| Potential Privacy Problems........................................................................................9 | |\n| 3.3. | Discrimination and Reputational Concerns..............................................................10 | |\n| 3.4. | Economic Concerns.................................................................................................11 | |\n| 3.5. | Health Outcome Concerns ......................................................................................11 | |\n| 3.6. | Other Potential Future Concerns.............................................................................11 | |\n| 3.7."}], "metadata": {"source": "Cybersecurity of Genomic Data", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Understanding Stablecoin Technology and Related Security Considerations:\n\nIt may be possible for malicious users to engineer a scenario (e.g., via social engineering to obtain credentials or exploiting a weakness in the software development environment or deployment software) in which they obtain the ability to deploy updated versions of the stablecoin's smart contract. In such a scenario, as the attacker gains full control, they remove the ability for the original smart contract managers to further modify the smart contract - essentially hijacking the stablecoin system.\n\nCeFi exchanges resemble a combination of a brokerage firm and a stock market exchange that deals only in cryptocurrencies. Users can create custodial accounts on CeFi exchanges just like they can with brokerage firms (often only after providing identity-proofing information). Each account may have two sub accounts that operate differently: one for fiat currency and one for cryptocurrency. Each fiat currency account acts like a typical cash account with a brokerage firm. The exchange is the custodian (i.e., they possess the currency) and uses an internal database to record the level of currency in each user account.\n\nEach cryptocurrency account has a private/public keypair like a typical account created with a cryptocurrency wallet. However, in this case, the exchange holds the private key and only provides the users with their public key/account number. Using this information, a user can transfer cryptocurrency into their account but not out of it. To transfer funds out of it (e.g., to a wallet account that the user controls, to an account on another exchange, or to make a direct payment), the user authenticates to the exchange (e.g., using a multi-factor authentication approach) and requests that the exchange initiate the transfer with the user's private key."}], "metadata": {"source": "Understanding Stablecoin Technology and Related Security Considerations", "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 Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\n................................................................. 40\n3.2.4 Define and Analyze Specific Alternatives ..................................................................................\n43\n3.2.5 Develop Recommendations ...................................................................................................... 46"}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering 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 Incident Response?"}, {"role": "assistant", "content": "According to Security Recommendations for Server-based Hypervisor Platforms:\n\n|\n| HY-SR-17 | VM configuration management tools should have the capability to compile logs and alert administrators when configuration changes are detected in any VM that is being monitored.\n| HY-BF4 (VM Lifecycle Management) |\n| HY-SR-18 | The access control solution for VM administration should have the granular capability both at the permission assignment level as well as at the object level (i.e., the specification of the target of the permission can be a single VM or any logical grouping of VMs - based on function or location). In addition, the ability to deny permission to some specific objects within a VM group (e.g., VMs running workloads of a particular sensitivity level) despite having access permission to the VM group | HY-BF4 (VM Lifecycle Management) |\n| HY-SR-19 | The administration of all hypervisor installations in the enterprise should be performed centrally using an enterprise virtualization management system (EVMS). Further enterprise gold-standard hypervisor configurations for different types of workloads and clusters must managed (enforced) through EVMS. The gold-standard configurations should at the minimum cover the following aspects - CPU, Memory, Storage, Network bandwidth and Host OS hardening (if required). | HY-BF5 (Management of hypervisor Platform) |\n| HY-SR-20 | Protection for Hypervisor Host &Software administration functions should be ensured by allocating a dedicated physical NIC, or if that is not feasible, by placing the management interface of the hypervisor in a dedicated virtual network segment and enforcing traffic controls using a firewall (e.g., designating the subnets in the enterprise network from which incoming traffic into the management interface is allowed). | HY-BF5 (Management of hypervisor Platform) |"}], "metadata": {"source": "Security Recommendations for Server-based Hypervisor Platforms", "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 Media Protection?"}, {"role": "assistant", "content": "According to ISCMA_ An Information Security Continuous Monitoring Program Assessment:\n\n| 3.5 | Assessment Parameters............................................................................................23 | Assessment Parameters............................................................................................23 | | |-------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| | 3.6 | Element Evaluation ...................................................................................................25 | Element Evaluation ...................................................................................................25 | | | | 3.6.1 | Judgment Selection ....................................................................................................28 | | | | 3.6.2 | Element-Level Judgment Assistance ..........................................................................28 | | | 3.7 | Scoring and Partial Results........................................................................................29 | Scoring and Partial Results........................................................................................29 | | | 3.8 | Action Buttons ..........................................................................................................31 | Action Buttons ..........................................................................................................31 | | | | 3.8.1 | Restart Assessment ....................................................................................................31 | | | | 3.8.2 | Merge Assessments....................................................................................................31 | | | | 3.8.3 | Export Data.................................................................................................................31 | | | | 3.8.4 | Tailor Assessment.......................................................................................................31 | | | 3.9 | Deploying the Workbook ..........................................................................................32 | Deploying the Workbook ..........................................................................................32 | | | 3.10 | Additional Underlying Worksheets ...........................................................................32 | Additional Underlying Worksheets ...........................................................................32 | | | 4 | The Principal Assessment Workbook...................................................................."}], "metadata": {"source": "ISCMA_ An Information Security Continuous Monitoring Program Assessment", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Federal Information and Information Systems:\n\n## 5. Maintenance Agency.\n\n1 An information system is a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. Information resources include information and related resources, such as personnel, equipment, funds, and information technology.\n\nThe minimum security requirements cover seventeen security-related areas with regard to protecting the confidentiality, integrity, and availability of federal information systems and the information processed, stored, and transmitted by those systems. The security-related areas include: (i) access control; (ii) awareness and training; (iii) audit and accountability; (iv) certification, accreditation, and security assessments; (v) configuration management; (vi) contingency planning; (vii) identification and authentication; (viii) incident response; (ix) maintenance; (x) media protection; (xi) physical and environmental protection; (xii) planning; (xiii) personnel security; (xiv) risk assessment; (xv) systems and services acquisition; (xvi) system and communications protection; and (xvii) system and information integrity. The seventeen areas represent a broad-based, balanced information security program that addresses the management, operational, and technical aspects of protecting federal information and information systems."}], "metadata": {"source": "Minimum Security Requirements for Federal Information and 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 Planning?"}, {"role": "assistant", "content": "According to Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities:\n\nThere may be references in this publica/t\\_i.ligaon to other publica/t\\_i.ligaons currently under development by NIST in accordance with its assigned statutory responsibili/t\\_i.ligaes. The informa/t\\_i.ligaon in this publica/t\\_i.ligaon, including concepts and methodologies, may be used by federal agencies even before the comple/t\\_i.ligaon of such companion publica/t\\_i.ligaons. Thus, un/t\\_i.ligal each publica/t\\_i.ligaon is completed, current requirements, guidelines, and procedures, where they exist, remain opera/t\\_i.ligave. For planning and transi/t\\_i.ligaon purposes, federal agencies may wish to closely follow the development of these new publica/t\\_i.ligaons by NIST. Organiza/t\\_i.ligaons are encouraged to review all dra/f\\_t.liga publica/t\\_i.ligaons during public comment periods and provide feedback to NIST. Many NIST cybersecurity publica/t\\_i.ligaons, other than the ones noted above, are available at h/t\\_t.ligaps://csrc.nist.gov/publica/t\\_i.ligaons."}], "metadata": {"source": "Bug Framework (BF)_ Formalizing Cybersecurity Weaknesses and Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Measuring the Usability and Security of Permuted Passwords on Mobile Platforms:\n\nfile called a password file , which often has corresponding operating system level logical access control mechanisms (e.g., file permissions) in place to prevent the reading and writing of this file.\nThe passwords of many users are often stored in the same password file alongside their associated username."}], "metadata": {"source": "Measuring the Usability and Security of Permuted Passwords on Mobile Platforms", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Notional Supply Chain Risk Management Practices for Federal Information Systems:\n\n| Reports on Computer Systems Technology_______________________ | Reports on Computer Systems Technology_______________________ | Reports on Computer Systems Technology_______________________ | |-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| | NIST Interagency Reports ____________________________________iii | NIST Interagency Reports ____________________________________iii | NIST Interagency Reports ____________________________________iii | | Authority __________________________________________________iv | Authority __________________________________________________iv | Authority __________________________________________________iv | | Acknowledgements __________________________________________ v | Acknowledgements __________________________________________ v | Acknowledgements __________________________________________ v | | Abstract ___________________________________________________ v | Abstract ___________________________________________________ v | Abstract ___________________________________________________ v | | Keywords __________________________________________________ v | Keywords __________________________________________________ v | Keywords __________________________________________________ v | | 1 Introduction _____________________________________________ 1 | 1 Introduction _____________________________________________ 1 | 1 Introduction _____________________________________________ 1 | | 1.1 | Purpose ______________________________________________________________ | 2 | | 1.2 | Scope ________________________________________________________________ | 3 | | 1.3 | Background___________________________________________________________ | 4 | | 1.4 | Related Documents_____________________________________________________ | 4 | | 1.5 | Document Structure____________________________________________________ | 5 | | 2 | Overview ________________________________________________ | 6 | | 2.1 Challenges _____________________________________________________________ 6 | 2.1 Challenges _____________________________________________________________ 6 | 2.1 Challenges _____________________________________________________________ 6 | | 2.2 | Foundational Practices _________________________________________________ | 7 | | 3 Implementing Supply Chain Risk Management _______________ 11 | 3 Implementing Supply Chain Risk Management _______________ 11 | 3 Implementing Supply Chain Risk Management _______________ 11"}], "metadata": {"source": "Notional Supply Chain Risk Management Practices 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 Security Assessment?"}, {"role": "assistant", "content": "According to Guide to SSL VPNs:\n\nSome of the cryptographic requirements, including allowable hash functions and certificate key lengths, will change at the end of 2010. Therefore, Federal agencies who want to provide SSL VPN services after 2010 must ensure that their systems are upgradeable to the new FIPS-compliant cipher suites and key lengths before the end of 2010, and that their SSL VPN vendors guarantee that such upgrades will be available early enough for testing and deployment in the field. 1. Identify Requirements. The first phase of the process involves identifying the current and future requirements for remote access and determining how they can best be met by an SSL VPN implementation. Determining requirements for U.S. federal agencies also means assessing how to comply with FIPS 140-2. 2. Design the Solution. The second phase involves all aspects of designing an SSL VPN solution. The design elements are grouped into five categories: access control, endpoint security, authentication methods, architecture, and cryptography policy. 3. Implement and Test a Prototype. The next phase involves implementing and testing a prototype in a laboratory or test environment. The primary goals are to evaluate all aspects of the solution including authentication, application compatibility, management, logging, performance, security of the implementation, design and layout of the VPN portal, and default settings. 4. Deploy the Solution. Once testing is completed and all issues are resolved, the next phase includes the deployment of the SSL VPN throughout the enterprise. This phase addresses issues specific to SSL VPNs that may occur during deployment. Support must be addressed, and this includes the process of working with a help desk to provide assistance for end users. 5. Manage the Solution. After the SSL VPN solution has been deployed, it must be managed throughout its lifecycle."}], "metadata": {"source": "Guide to SSL VPNs", "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 ISCMA_ An Information Security Continuous Monitoring Program Assessment:\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- NIST SP 800-137 [SP800-137] describes the desirable properties of an ISCM program and the process for establishing an ISCM program in an organization.\n- NIST SP 800-137A [SP800-137A] provides guidance on the development of an ISCM program assessment and describes the desirable properties of an ISCM program assessment methodology and the process for assessing the effectiveness of an ISCM program in an organization. The assessment methodology described in SP 800-137A has been followed in this report and implemented in the [ISCMAx] companion tool."}], "metadata": {"source": "ISCMA_ An Information Security Continuous Monitoring Program Assessment", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance):\n\n| 1. INTRODUCTION.....................................................................................................................1 | 1. INTRODUCTION.....................................................................................................................1 | 1. INTRODUCTION.....................................................................................................................1 | 1."}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Notional Supply Chain Risk Management Practices for Federal Information Systems:\n\n3.2.6 Operational Contract Execution\n\nOnce a system becomes operational, the operating environment may change."}], "metadata": {"source": "Notional Supply Chain Risk Management Practices for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.2.6", "cmmc_practice_id": "AT.L2-3.2.6", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities:\n\n[IR7864] | Practices | Tasks | Notional Implementation Examples | References | |-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Prepare the Organization (PO) | | | | | Define Security Requirements for Software Development (PO.1) : Ensure that security requirements for software development are known at all times so that they can be taken into account throughout the SDLC and duplication of effort can be minimized because the requirements information can be collected once and shared."}], "metadata": {"source": "Secure Software Development Framework (SSDF) Version 1.1_ Recommendations for Mitigating the Risk of Software Vulnerabilities", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Guide to Operational Technology (OT) Security:\n\n3.3.5. 3.3.5."}], "metadata": {"source": "Guide to Operational Technology (OT) Security", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices:\n\nType.............................................................98 | | | C.3.5.8 System and Network Monitoring Information Type...............................................100 | | | C.3.5.9 Information Sharing Information Type...................................................................101 | | | APPENDIX D: IMPACT DETERMINATION FOR MISSION-BASED INFORMATION AND INFORMATION SYSTEMS......................................................102 | | | D.2 Homeland Security.............................................................................................................."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guidelines for Derived Personal Identity Verification (PIV) Credentials:\n\n-  Communication between the issuer and the cryptographic module in which the Derived PIV Authentication private key is stored shall occur only over mutually authenticated secure sessions between tested and validated cryptographic modules. 5\n-  Data transmitted between the issuer and the cryptographic module in which the Derived PIV Authentication private key is stored shall be encrypted and contain data integrity checks.\n\n-  If the Derived PIV Credential is issued by the same agency or issuer that issued the Subscriber's PIV Card, then the Derived PIV Credential issuer may have direct access to the Identity Management System (IDMS) database implemented by the issuing agency that contains the relevant information about the Subscriber.\n-  When the issuer of the Derived PIV Credential is different from the PIV Card Issuer, the following mechanisms may be applied:\n- o The Backend Attribute Exchange [BAE] can be queried for the termination status of the PIV Card, if an attribute providing this information is defined and the issuer of the PIV Card maintains this attribute for the Subscriber. The BAE can also be queried for other attributes about the Subscriber (e.g., name) that may appear in the Derived PIV Authentication certificate.\n- o The issuer of the Derived PIV Credential notifies the original PIV issuer when a Derived PIV Credential is created. The issuer of the PIV Card maintains a list of corresponding Derived PIV Credential issuers and sends notification to the latter set when the PIV Card is terminated or when attributes about the cardholder change. Such notification should provide evidence of receipt and the integrity of the message.\n- o If a Uniform Reliability and Revocation Service (URRS) is implemented in accordance with Section 3.7 of [NISTIR7817], the issuer of a Derived PIV Credential may obtain termination status of the Subscriber's PIV Card through the URRS."}], "metadata": {"source": "Guidelines for Derived Personal Identity Verification (PIV) Credentials", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Stateful Hash-Based Signature Schemes:\n\n|\n| [12] | Buchmann J, Dahmen E, Hulsing A (2011) XMSS - A Practical Forward Secure Signature Scheme based on Minimal Security Assumptions .\nCryptology ePrint Archive , Report 2011/484. https://eprint.iacr.org/2011/484.pdf |\n| [13] | Bruinderink LG, Hülsing A (2016) 'Oops, I did it again' - Security of One- Time Signatures under Two-Message Attacks. Cryptology ePrint Archive , Report 2016/1042. https://eprint.iacr.org/2016/1042.pdf |\n| [14] | Perlner R, Cooper D (2009) Quantum Resistant Public Key Cryptography: A Survey. 8th Symposium on Identity and Trust on the Internet (IDtrust 2009) , pp 85-93. https://doi.org/10.1145/1527017.1527028 |\n| [15] | Eaton E (2017) Leighton-Micali Hash-Based Signatures in the Quantum Random-Oracle Model. Cryptology ePrint Archive , Report 2017/607. https://eprint.iacr.org/2017/607 |\n| [16] | Bernstein DJ, Hülsing A, Kölbl S, Niederhagen R, Rijneveld J, Schwabe P (2019) The SPHINCS+ Signature Framework. Cryptology ePrint Archive , Report 2019/1086. https://eprint.iacr.org/2019/1086.pdf |\n| [17] | Malkin T, Micciancio D, Miner S (2002) Efficient generic forward-secure signatures with an unbounded number of time periods. Advances in Cryptology -EUROCRYPT 2002 , Lecture Notes in Computer Science 2332, pp 400-417. https://doi.org/10.1007/3-540-46035-7_27 |\n| [18] | Merkle RC (1979) Security, Authentication, and Public Key Systems . PhD thesis, Stanford University, June 1979."}], "metadata": {"source": "Recommendation for Stateful Hash-Based Signature Schemes", "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 Guidelines for API Protection for Cloud-Native Systems:\n\n...............14 |\n| 2.7.5. Reaching Out to Other Systems .................................................................................................15 |\n| 2.7.7.\nIdentity Canonicalization............................................................................................................16 |\n| 3. Recommended Controls for APIs...................................................................................................17 |\n| 3.1.1. Basic Pre-Runtime Protections...................................................................................................18 |\n| 3.1.2. Advanced Pre-Runtime Protections ...........................................................................................19 |\n| 3.2.1. Basic Runtime Protections..........................................................................................................20 |"}], "metadata": {"source": "Guidelines for API Protection for Cloud-Native Systems", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\n| Scope..............................................................................................................\n| 2 |\n| | 1.2.1 Alternative Configurations | ....................................................................3 |\n| 1.3 | Document Conventions................................................................................... | 3 |\n| 2 TLS Overview .........................................................................................................4 | 2 TLS Overview .........................................................................................................4 | 2 TLS Overview .........................................................................................................4 |\n| 2.1 | TLS Subprotocols | ..........................................................................................."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities:\n\n3.2.1 | Base Equation ... 3.2.1 Base Equation\n\nThe base equation is the foundation of CCSS scoring."}], "metadata": {"source": "The Common Configuration Scoring System (CCSS)_ Metrics for Software Security Configuration Vulnerabilities", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Integrating Cybersecurity and Enterprise Risk Management (ERM):\n\nAir Force; U.S. Department of Defense; U.S. At higher levels in the enterprise structure, those cybersecurity and other risk registers are aggregated, normalized, and prioritized into risk profiles .\nA risk profile is defined by OMB Circular A-123 as 'a prioritized inventory of the most significant risks identified and assessed through the risk assessment process versus a complete inventory of risks' [3]. While it is critical that enterprises address potential negative impacts on mission and business objectives, it is equally critical (and required for federal agencies) that enterprises plan for success. OMB states in Circular A-123 that 'the [Enterprise Risk] profile must identify sources of uncertainty, both positive (opportunities) and negative (threats).' Enterprise-level decision makers use the risk profile to choose which enterprise risks to address, allocate resources, and delegate responsibilities to appropriate risk owners. ERM programs should define terminology, formats, criteria, and other guidance for risk inputs from lower levels of the enterprise."}], "metadata": {"source": "Integrating Cybersecurity and Enterprise Risk Management (ERM)", "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 PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance):\n\n| A.4.2.2 | VERIFY | Provides the key reference for PIV Card Application PIN, Global PIN, pairng code, or OCC as well as its corresponding value.\nSets/updates the PIV Card Application security status on the card; optionally (according to discovery object) establishes VCI with pairing code after pivEstablishSecureMessaging is invoked. |\n| pivLogOutOfCardApplication | A.4.2.4 | VERIFY | Resets the security status on all local key references. |\n| pivGetData | A.4.2.3 | GET DATA | Maps the OID to BER-TLV tag for the selected object. |\n| pivPutData | A.4.4.1 | PUT DATA | Maps the OID to BER-TLV tag for the selected object. |\n| pivGenerateKeyPair | A.4.4.2 | GENERATE ASYMMETRIC KEY PAIR | Passes the key reference and cryptographic mechanism identifier value. |\n| pivCrypt | A.4.3.1 | GENERAL AUTHENTICATE | Passes the key reference, cryptographic algorithm reference and the string to be acted upon. Sets/updates the PIV Card Application security status on the card, if applicable. |\n| pivMiddlewareVersion | A4.1.3 | No equivalent command | Returns the PIV Middleware version supported by the PIV Middleware IUT. |\n| pivEstablishSecureMessaging | A.4.2.5 | GENERAL AUTHENTICATE 5 | Passes the key reference and cryptographic algorithm reference to the PIV Card Application in order to establish secure messaging. Establishes, controls, and maintains the session key. |"}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "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 Awareness and Training?"}, {"role": "assistant", "content": "According to Approaches and Challenges of Federal Cybersecurity Awareness Programs:\n\n## Approaches and Challenges of Federal Cybersecurity Awareness Programs\n\n## Approaches and Challenges of Federal Cybersecurity Awareness Programs\n\nOrganizational security awareness programs experience a number of challenges, including lack of resources, difficulty measuring the impact of the program, and perceptions among the workforce that training is a boring, 'check-the-box' activity. While prior surveys and research have examined programs in the private sector, there is little understanding of whether these findings also apply within the U.S. government. To address this gap and better understand the needs, challenges, practices, and necessary competencies of federal security awareness teams and programs, NIST conducted a research study that leveraged both qualitative and quantitative methodologies. This companion document to NISTIR 8420 'Federal Cybersecurity Awareness Programs: A Mixed Methods Research Study' reports on a subset of study results focused on identifying the current approaches and challenges of security awareness programs within the federal government. Insights gained from these results are informing guidance and other initiatives to aid federal organizations in building effective security awareness programs. While focused on the U.S. government, findings may also have implications for organizational security awareness programs in other sectors."}], "metadata": {"source": "Approaches and Challenges of Federal Cybersecurity Awareness Programs", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Technical Guide to Information Security Testing and Assessment:\n\nis most effective when system files are compared with a reference database created using a system known to be secure-this helps ensure that the reference database was not built with compromised files.\nThe reference database should be stored offline to prevent attackers from compromising the system and covering their tracks by modifying the database. In addition, because patches and other updates change files, the checksum database should be kept up-todate."}], "metadata": {"source": "Technical Guide to Information Security Testing and Assessment", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Foundations of a Security Policy for Use of the National Research and Educational Network:\n\nMost of the current research deals with the technical issues of enforcing specific aspects of security e.g. access controls and encryption. Comparatively little attention has been given to the development of a meaningful and generally accepted 'policy' for information security that would be applicable to a diverse set of users and computers in interconnected networks. 1. The NREN will evolve from the existing Internet base and will have to fit into an international environment sponsored or owned by non-U.S. organizations. 2. Special purpose networks and mission-oriented networks (sponsored by the U.S. government) will need to link with, if not directly support, the NREN. 3. The architecture must accommodate the use of commercial services, private and governmentsponsored networks. 4. The architecture will continue to be layered set of protocols although it may differ from present Internet and planned OSI structures in some respects. 5. The system will support multiple protocols, including at lecist full TCP/IP and OSI protocol stacks, on an end-to-end basis. 6. The architecture must accommodate local areas networks (LANS), metropolitan area networks (MANS), regional networks, and wide-area networks (WANS) - some of which will support transit (pass through) traffic originating and terminating in other networks. 7. A variety of current and evolving technologies may be used including such things as high-speed Fiber Data Distributed Interface (FDDI), Distributed-Queue Dual Bus (DQDB), broadband Integrated Services Digital Network (ISDN) utilizing Asynchronous Transfer Mode (ATM) switching as well as conventional Token Ring, Ethernet, and other technologies. 8. Services accessible through the NREN will include various kinds of servers for general support (network management facilities, name servers, electronic mail, database servers, multicast routers, cryptographic certificate servers), collaboration support tools (video/teleconferencing), and other groupware facilities."}], "metadata": {"source": "Foundations of a Security Policy for Use of the National Research and Educational Network", "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 BowTie – A deep learning feedforward neural network for sentiment analysis provide? (Part 4)"}, {"role": "assistant", "content": "rchers argue that the gradient descent method has an implicit bias that is not yet fully understood, especially in cases where there are multiple solutions that properly classify a given dataset [14].\nThus, it is important to have a neural network with low loss estimates for a trained model to hope for a good and reliable transfer accuracy. The primary goal of this paper is to shed light on how to address these issues in practice. To do this, I introduce a new feedforward neural network for sentiment analysis and draw on the experiences from using it with two different types of word encoding: a simple one based on the word ranking in the dataset vocabulary; the other judiciously enhanced with meta-data related to word polarity. The main contribution of this paper is the design of the BowTie neural network in Section 2. ## 1 Data encoding and datasets\n\nAs discussed above, there are many different types of encodings of text with different complexity and degree of effectiveness. Since there is no convincing positive correlation established in the literature between complexity of the encoding and higher prediction accuracy, it is important to investigate the extent to which simple data encodings can be used for sentiment analysis. Simpler encodings have been shown to be robust and efficient [3]. But can they provide high prediction accuracy in sentiment analysis? I investigate this open question by evaluating the accuracy one may attain using two types of text encoding on representative benchmark datasets. ## 1.1 Multi-hot encoding\n\nThe first encoding is the multi-hot encoding of text [6] which can be defined as follows. Figure 1. A multi-hot encoded text in D, Π D with M = 88 587 . Figure 2. A polarityweighted multi-hot encoded text in D, Π D with M = 89527 . \n\nLet π be a linguistic type (e.g. morpheme, word) and let Π D be the set of all such linguistic types in a dataset D . Let M = | Π D | be the cardinality of Π D ."}], "metadata": {"source": "BowTie – A deep learning feedforward neural network for sentiment analysis", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\n......................22 |\n| 2.3.3. Risk Transfer................................................................................................................................22 |\n| 2.3.4.\nRisk Mitigation.............................................................................................................................23 |\n| 2.3.5. Relationship of Risk Response to Risk Strategy ..........................................................................26 |\n| 2.3.6. Implicit Acceptance.....................................................................................................................28 |\n| 2.3.7. Responding to Positive Risk Scenarios ........................................................................................30 |\n| 2.4.1. Risk Response Cost......................................................................................................................31 |\n| 2.4.2. Risk Response Description ..........................................................................................................32 |\n| 2.4.4. Status...........................................................................................................................................34 |\n| Conclusion ...................................................................................................................................36 |\n| 3. |\n| Appendix B. Change Log...................................................................................................................41 |"}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study:\n\nUnfortunately, security awareness efforts may face significant challenges. Industry surveys and research studies have discovered that security awareness programs in organizations of all sizes may be underfunded and often rely on part-time security awareness professionals who may lack sufficient background, skills, tools, or resources necessary for managing an effective program [SANS][WOELK][BADA][STEWART]. Furthermore, employees may view training as boring and burdensome [BADA]. While mandates enforce a minimum baseline for security awareness, when viewed simply as a 'check-the-box' exercise, organizations may begin to measure program success simply in terms of compliance metrics, like training completion rates. However, these metrics reveal little about the effectiveness of the training in changing and sustaining workforce attitudes and behaviors [FERTIG]."}], "metadata": {"source": "Federal Cybersecurity Awareness Programs_ A Mixed Methods Research Study", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\nThe IT personnel also installed and configured a Historian database on the manufacturing floor to record manufacturing process data. IT personnel are responsible for regular data backup of the Historian, and the manufacturing engineers are responsible for the configuration and operation of the Historian. 1. IT assets must only be used for the business activities they are assigned and authorized to perform. 2. Every employee is responsible for the preservation and proper use of the IT assets they have been assigned. 3. IT assets must not be left unduly exposed. 4. Desktops and laptops must be locked if left unattended. This policy should be automatically enforced whenever possible. 5. IT assets must not be accessed by non-authorized individuals. Authorization can be obtained from Director of Operations. 6. Configuration changes are to be conducted through the change control process, identifying risks and noteworthy implementation changes. 7. All assets must be protected by authentication technologies (e.g., passwords). 8. Passwords must follow the password policy. 9. The Director of Operations must be notified immediately after an asset is discovered to be lost or stolen. 10. Use of personal devices to access IT resources is prohibited. 11. Storage of sensitive information on portable media is prohibited, unless authorized by the Director of Operations. 12. Any sensitive information stored on IT assets, or being transported on a portable device, must be protected in such a way to deny unauthorized access, and must be encrypted in line with industry best practices and any applicable laws or regulations. 1. OT assets must not be used for operations they are not assigned or authorized to perform. 2. The Director of Operations and Operators are responsible for the preservation and correct use of the OT assets they have been assigned. 3. Physical access to OT assets is forbidden for non-authorized personnel. 4."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "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 Automation Support for Security Control Assessments_ Software Vulnerability Management:\n\na) | FLAW REMEDIATION | TIME TO REMEDIATE FLAWS / BENCHMARKS FOR CORRECTIVE ACTIONS The organization: (a) Measures the time between flaw identification and flaw remediation.\n|\n| SI-2(3)(b) | FLAW REMEDIATION | TIME TO REMEDIATE FLAWS / BENCHMARKS FOR CORRECTIVE ACTIONS The organization: (b) Establishes [Assignment: organization-defined benchmarks] for taking corrective actions. |\n| SI-2(5) | FLAW REMEDIATION | AUTOMATIC SOFTWARE / FIRMWARE UPDATES The organization installs [Assignment: organization-defined security-relevant software and firmware updates] automatically to [Assignment: organization- defined information system components]. |\n| SI-2(6) | FLAW REMEDIATION | REMOVAL OF PREVIOUS VERSIONS OF SOFTWARE / FIRMWARE The organization removes [Assignment: organization-defined software and firmware components] after updated versions have been installed. |\n| SI-3(10)(b) | MALICIOUS CODE PROTECTION | MALICIOUS CODE ANALYSIS The organization: (b) Incorporates the results from malicious code analysis into organizational incident response and flaw remediation processes. |\n| SI-14 | NON-PERSISTENCE Control: The organization implements non-persistent [Assignment: organization-defined information system components and services] that are initiated in a known state and terminated [Selection (one or more): upon end of session of use; periodically at [Assignment: organization-defined frequency]]. |\n| SI-14(1) | NON-PERSISTENCE | REFRESH FROM TRUSTED SOURCES The organization ensures that software and data employed during information system component and service refreshes are obtained from [Assignment: organization-defined trusted sources]. |"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Software Vulnerability 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 require for Access Control?"}, {"role": "assistant", "content": "According to Guide to Intrusion Detection and Prevention Systems (IDPS):\n\n| Introduction ......................................................................................................................1-1 | Introduction ......................................................................................................................1-1 | | | 1.1 | | Authority...................................................................................................................1-1 | | | | 1.2 | Purpose and Scope .................................................................................................1-1 | | | | 1.3 | Audience..................................................................................................................1-1 | | | | 1.4 | Document Structure.................................................................................................1-1 | | | | Intrusion Detection and Prevention Principles .............................................................2-1 | Intrusion Detection and Prevention Principles .............................................................2-1 | | | 2."}], "metadata": {"source": "Guide to Intrusion Detection and Prevention Systems (IDPS)", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to 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 is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Guidelines for the Secure Deployment of IPv6:\n\n3.2.1 IPv6 Address Assignments ... 3.2.1 IPv6 Address Assignments ... 3.2.1 describes address assignments using leftmost, rightmost, and centermost strategies."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "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 is CMMC practice AT.L2-3.2.7 (NIST 3.2.7)?"}, {"role": "assistant", "content": "According to Guide to Bluetooth Security:\n\n3.2.7 Bluetooth Link Key Derivation from Low Energy Long TermKey... 3.2.7 Bluetooth Link Key Derivation from Low Energy Long TermKey... 3.2.7 for details."}], "metadata": {"source": "Guide to Bluetooth Security", "cmmc_level": "all", "nist_control": "3.2.7", "cmmc_practice_id": "AT.L2-3.2.7", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP) provide? (Part 2)"}, {"role": "assistant", "content": "ral agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative.\nFor planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Automated Secure Configuration Guidance from the macOS Security Compliance Project (mSCP)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Guidelines on PDA Forensics:\n\n- „ Testability - Has the scientific theory or technique been empirically tested? According to K. Popper (1989) in The Growth of Scientific Knowledge, \"the criterion on the scientific status of a theory is its falsifiability, refutability, and testability.\"\n- „ Acceptance - Has the scientific theory or technique been subjected to peer review and publication? This ensures that flaws in the methodology would have been detected and that the technique is finding its way into use via the literature. - „ Error Rate - What is the known or potential error rate? Scientific measures generally have associated error rates, which can be estimated with a fair amount of precision. Known threats exist against the validity and reliability in any test (experimental and quasi-experimental) of a theory. - „ Credibility - What is the expert's qualifications and stature in the scientific community? Does the technique rely upon the special skills and equipment of one expert, or can it be replicated by other experts elsewhere? - „ Clarity - Can the technique and its results be explained with sufficient clarity and simplicity so that the court and the jury can understand its plain meaning? This criterion is assumed to be incorporated in Daubert implicitly. - „ Gain access through a hardware backdoor - Hardware backdoors, such as interfaces for debugging, production testing, or maintenance, may be used to gain access to memory. For example, some devices have active hardware test points on the circuit board that can be used to probe the device. Many manufacturers now support the JTAG (Joint Test Action Group) standard, which defines a common test interface for processor, memory, and other semiconductor chips, on their devices [Int96]. Forensic examiners can communicate with a JTAG-compliant component by utilizing software and an add-in hardware controller in a personal computer card slot or a special purpose stand-alone programmer device to probe defined test points."}], "metadata": {"source": "Guidelines on PDA Forensics", "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 Computer Security Division 2004 Annual Report provide? (Part 2)"}, {"role": "assistant", "content": "4 was a challenge from the President, issued in Homeland Security Presidential Directive #12, to develop a new standard for identification and verification of Federal employees and contractors.\nWe continued making progress in fulfilling the mandates of the Federal Information Security Management Act of 2002 which resulted in Federal Information Processing Standard (FIPS) 199, Standards for Security Categorization of Federal Information and Information Systems , and NIST Special Publication (SP) 800-53, Recommended Security Controls for Federal Information Systems . In addressing the President's challenge, we drew heavily upon our ongoing smart card, biometric and cryptographic work. As such, we made great strides towards a framework for protecting Federal facilities, systems and the employees who have access to them. The long-term benefit of using FIPS 199, SP 800-53 and a standards-based approach to system security in general is more targeted, costeffective, consistent and improved security. While the interconnection of information systems often increases the risk to an organization's operations and assets, FIPS 199 and our associated suite of standards and guidelines provide a common way to express information security requirements. This in turn promotes greater consistency across diverse organizations in managing risks. Scientists in the Computer Security Division have been working with our partners for the past several years to establish a Government Smart Card (GSC) program to facilitate widespread deployment of interoperable smart card systems. In recognition of this work, the NIST Smart Card Team received the Department of Commerce's 2004 Gold Medal Award for the development of a framework and specification that dramatically advanced interoperability among smart card applications, coalesced U.S."}], "metadata": {"source": "Computer Security Division 2004 Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\n3.1.5. 3.1.5."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IR.L2-3.6.2 (NIST 3.6.2)?"}, {"role": "assistant", "content": "According to A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N:\n\n3.6.2 Access Request Processing in Delegation Chains... 3.6.2 Access Request Processing in Delegation Chains\n\nIn the absence of any delegation chain, all access policies in the system are (trusted) Access Policies."}], "metadata": {"source": "A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N", "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 does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\nThere may be references in this publication to other publications currently under development by NIST in 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\nBy keeping metrics consistent over time, organizations can evaluate long-term trends and related to metrics over a continuous period (e.g., quarter to quarter, year to year) will give more information about the success of organization-, program-, and system-level information security plans, policies, procedures, and goals. Some metrics may be gathered because of external guidance or regulations.\n\nImplementation measures demonstrate the progress of specific controls. Monitoring implementation may include assessment results, such as a tally of known systems or a binary 'yes/no' about which systems have up-to-date patches. 9 Implementation measures look at quantitative outputs and are usually demonstrated in percentages. Examples of implementation measures related to information security programs include the percentage of systems with approved system security plans and the percentage of systems with password policies that are configured as required. Implementation measures can also examine systemlevel areas, such as the percentage of servers in a system with a standard configuration."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "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 AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Guide for Mapping Types of Information and Information Systems to Security Categories:\n\n3.1.1 | Security Categories... 3.1.1 Security Categories\n\nFIPS 199 establishes security categories for both information 6 and information systems."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\n- improvement opportunities for the organization's policies, plans, processes, procedures, and practices that support cybersecurity risk management to inform efforts under all six Functions. - PROTECT (PR) -Safeguards to manage the organization's cybersecurity risks are used. Once assets and risks are identified and prioritized, PROTECT supports the ability to secure those assets to prevent or lower the likelihood and impact of adverse cybersecurity events, as well as to increase the likelihood and impact of taking advantage of opportunities. Outcomes covered by this Function include identity management, authentication, and access control; awareness and training; data security; platform security (i.e., securing the hardware, software, and services of physical and virtual platforms); and the resilience of technology infrastructure. - DETECT (DE) -Possible cybersecurity attacks and compromises are found and analyzed. DETECT enables the timely discovery and analysis of anomalies, indicators of compromise, and other potentially adverse events that may indicate that cybersecurity attacks and incidents are occurring. This Function supports successful incident response and recovery activities. - RESPOND (RS) -Actions regarding a detected cybersecurity incident are taken. RESPOND supports the ability to contain the effects of cybersecurity incidents. Outcomes within this Function cover incident management, analysis, mitigation, reporting, and communication. - RECOVER (RC) -Assets and operations affected by a cybersecurity incident are restored. RECOVER supports the timely restoration of normal operations to reduce the effects of cybersecurity incidents and enable appropriate communication during recovery efforts. ## 3.1."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/4/final, including related content, potential updates, and document history.\n\n3.7.\n\ncollection, maintenance, use, and disclosure of information about individuals that\nis maintained by federal agencies in systems of records"}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security:\n\n| Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi | Executive Summary...................................................................................................................vi |\n|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction .........................................................................................................................1 | 1. Introduction .........................................................................................................................1 | 1."}], "metadata": {"source": "Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers” support CMMC certification?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\nts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## 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-05-06\n\n## How to Cite this NIST Technical Series Publication\n\nMegas, K, Fagan M, Cuthill B, Hoehn B , Petrella E (2025) Workshop Summary Report for 'Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' . (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8572. https://doi.org/10.6028/NIST.IR.8572\n\n## Author ORCID iDs\n\nKaterina Megas: 0000-0002-2815-5448\n\nMichael Fagan: 0000-0002-1861-2609\n\nBarbara Cuthill: 0000-0002-2588-6165\n\n## Contact Information\n\niotsecurity@nist.gov\n\nNational Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8572/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nThis report summarizes discussions held at the March 5, 2025 \"Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers' organized by the NIST Cybersecurity for the Internet of Things (IoT) program."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program provide? (Part 2)"}, {"role": "assistant", "content": "may wish to closely follow the development of these new publications by NIST. Organizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST.\nMany NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2024-11-04 Supersedes NIST SP 800-55 Rev."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management:\n\nThe device type or sub- components do not meet organization defined rules (for removal and/or connection). | Assessment Criteria Notes: 1) The actual state includes four parts: a. the actual hardware configuration of devices approved for removal. The hardware configuration typically consists of the presence or absence of specific hardware subcomponents (e.g., DVD drives, USB ports). b. data identifying devices about to be used in travel (and to where). c. users authorized to take the devices on travel. d. data identifying devices reentering the assessment boundary (and where else the device has been connected while removed - this might be validated from GPS and IP logging, if appropriate). 2) The desired state includes two parts: a. the list of devices authorized for removal; and b. the desired hardware configuration and/or sanitization for such devices, based on connections while removed. [Reference 1a and 1d, above.] 3) A defect occurs when: a. any device unauthorized for removal is either expected to be (or has actually been) removed, regardless of hardware configuration. b. a device approved for travel does not have the desired hardware configuration for the proposed uses. c. a device approved for travel was connected to unapproved location(s) where its hardware configuration was not appropriate (matching the desired state) for those location(s). | TBD |"}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 2_ Hardware Asset Management", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Guide to Information Technology Security Services provide?"}, {"role": "assistant", "content": "\n\nSpecial Publication 800-35\n\n## Guide to Information Technology Security Services\n\nRecommendations of the National Institute of Standards and T echnology\n\nTim Grance Joan Hash Marc Stevens Kristofor O'Neal Nadya Bartol\n\nSpecial Publication 800-35\n\n## Guide to Information Technology Security Services\n\nThe National Institute of Standards and Technology\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\n\n\nOctober 2003\n\nU.S. Department of Commerce Donald L. Evans, Secretary\n\nTechnology Administration Phillip J. Bond, Under Secretary for Technology\n\nNational Institute of Standards and Technology Arden L. Bement, Jr., Director\n\n## Acknowledgements\n\nThe authors, Tim Grance and Joan Hash of the National Institute of Standards and Technology (NIST), and Marc Stevens, Kristofor O'Neal, and Nadya Bartol, of Booz Allen Hamilton (BAH), wish to thank their colleagues who reviewed the many drafts of this document and contributed to its technical content. We also gratefully acknowledge and appreciate the many comments we received from readers of the public and private sectors, whose valuable insights improved the quality and usefulness of this document. The authors would like to specifically acknowledge some key organizations whose extensive feedback substantially contributed to the development of the document. These organizations include: Environmental Protection Agency, Department of Treasury, Tennessee Valley Authority, and Electronic Data Systems. The authors would also like to acknowledge Ron Ross, Gary Stoneburner, Curtis Barker, Ron Tencati, Marianne Swanson, and Bill Burr of NIST, Alexis Feringa, Don Ottinger, Skip Hirsh, and Robert Young, BAH, and Shirley Radack for their extensive review and comment and keen and insightful assistance throughout the development of the document."}], "metadata": {"source": "Guide to Information Technology Security Services", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.3 (NIST 3.2.3)?"}, {"role": "assistant", "content": "According to An Introduction to Information Security:\n\n3.2.3 Using the System Security Plan (SSP)\n\nThe system security plan provides implementation details against which the system can be audited."}], "metadata": {"source": "An Introduction to Information Security", "cmmc_level": "all", "nist_control": "3.2.3", "cmmc_practice_id": "AT.L2-3.2.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Security Assessment?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\nAdvanced Persistent Threat; Basic Security Requirement; Contractor Systems; Controlled Unclassified Information; CUI Registry; Derived Security Requirement; Enhanced Security Requirement; Executive Order 13556; FIPS Publication 199; FIPS Publication 200; FISMA; NIST Special Publication 800-53; Nonfederal Organizations; Nonfederal Systems; Security Assessment; Security Control; Security Requirement. | CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security:\n\n.....................................................1 | 1. Introduction .........................................................................................................................1 | 1.\nIntroduction .........................................................................................................................1 | |\n| | 1.1 | Purpose and Scope | ....................................................................................................1 |\n| | 1.2 | Audience.....................................................................................................................1 | |\n| | 1.3 | Document Structure....................................................................................................1 | |\n| 2."}], "metadata": {"source": "Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. The authors, Kerry McKay and David Cooper of the National Institute of Standards and Technology (NIST), would like to thank the many people who assisted with the development of this document. In particular, we would like to acknowledge Tim Polk of NIST and Santosh Chokhani of CygnaCom Solutions, who were co-authors on the first revision of this document. We would also like to acknowledge Matthew J. Fanto and C."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\nA robust testing framework and guidance to provide assurance that a particular component or system is compliant with FIPS201 and supporting standards should exist to build the necessary PIV infrastructure to support common unified processes and systems for government-wide use. NIST developed test guidance in two parts. The first part addresses test requirements for interface to the PIV card and are provided in SP80085A. The second part provides test requirements for the PIV data model and is provided in this document. This document specifies the derived test requirements, and the detailed test assertions and conformance tests for testing the PIV data model. | 1. | Introduction ............................................................................................................1 | Introduction ............................................................................................................1 |\n|------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|\n| | 1.1 Authority | ..........................................................................................................1 |\n| | 1.2 Purpose | and Scope.........................................................................................1 |\n| | 1.3 Audience | and Assumptions.............................................................................2 |\n| 2."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Transitioning to the Security Content Automation Protocol (SCAP) Version 2:\n\nf configuration setting information from an endpoint using OVAL [19]. A NEA extension will be developed to allow for event-driven and ad-hoc OVAL-based collection of configuration setting information.\nThe OVAL and SCAP communities have requested improvements to OVAL that need to be considered to better integrate OVAL with other SCAP specifications, to improve OVAL functionality, to make OVAL content easier to create, and to increase overall OVAL adoption. These updates are expected to be worked on in an international standards organization."}], "metadata": {"source": "Transitioning to the Security Content Automation Protocol (SCAP) Version 2", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for 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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Security of SQL-Based Implementations of Product Data Exchange Using STEP:\n\nThis paper is intended for designers of systems and databases that use SQL in implementing STEP. With [PB93], this paper will help to evaluate the security controls of SQL with respect to different security policies. This evaluation should help determine the types of controls and mechanisms that will be required from the SQL processor(s), as well as other components of the system (such as operating system (OS) controls, network protocols, and identification and authentication mechanisms).\n\nThe interface between the SQL processor and STEP applications may utilize the embedded SQL language or the STEP Data Access Interface (SDAI) interface. The application must supply accurate information regarding the identity of the user to the SQL processor. This places two requirements on the system: appropriate selection\n\nand management of identification and authentication (I&A) controls and control of this critical attribute's propagation."}], "metadata": {"source": "Security of SQL-Based Implementations of Product Data Exchange Using STEP", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security Guidance for First Responder Mobile and Wearable Devices:\n\n| MTD | Mobile Threat Defense |\n|--------|------------------------------------------------|\n| MAC | Media Access Control Address |\n| MAV | Mobile Application Vetting |\n| NFC | Near Field Communication |\n| NIST | National Institute of Standards and Technology |\n| NPSBN | Nationwide Public Safety Broadband Network |\n| OS | Operating System |\n| OUI | Organizationally Unique Identifier |\n| PAN | Personal Area Network |\n| PIN | Personal Identification Number |\n| PMF | Protected Management Frame(s) |\n| PMK | Pairwise Main Key |\n| PTK | Pairwise Transient Key |\n| PITM | Person in the Middle |\n| PSCR | Public Safety Communications Research |\n| PSK | Pre-shared Key |\n| RFID | Radio-Frequency Identification |\n| RSN | Robust Security Network |\n| SNonce | Supplicant Number once |\n| SP | Special Publication |\n| SSID | Service Set Identifier |\n| SSL | Secure Sockets Layer |\n| SSO | Single Sign-on |\n| TLS | Transport Layer Security |\n| TPK | Temporal Pairwise Key |\n\nGaps: Network and systems administrators must take note of the MAC address randomization feature during device enrollment to ensure proper device connectivity and tracking. When a mobile device connects to a Wi-Fi network, it will save the randomized MAC address into a network profile. Subsequent associations to the same Wi-Fi network will utilize the saved network profile information."}], "metadata": {"source": "Security Guidance for First Responder Mobile and Wearable 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 are the CMMC Level 2 requirements?"}, {"role": "assistant", "content": "According to Hardware Security Failure Scenarios_ Potential Hardware Weaknesses:\n\naft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications.\n## 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-11-04\n\n## How to Cite this NIST Technical Series Publication\n\nMell P, Bojanova I (2024) Hardware Security Failure Scenarios: Potential Hardware Weaknesses. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8517. https://doi.org/10.6028/NIST.IR.8517\n\n## Author ORCID iDs\n\nPeter Mell: 0000-0003-2938-897X Irena Bojanova: 0000-0002-3198-7026\n\n## Contact Information\n\nnistir8517@nist.gov\n\nNational Institute of Standards and Technology Attn: Computer Security Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\n## Additional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/ir/8517/final, including related content, potential updates, and document history. All comments are subject to release under the Freedom of Information Act (FOIA). ## Abstract\n\nHardware is often assumed to be robust from a security perspective. However, chips are both created with software and contain complex encodings (e.g., circuit designs and firmware). This leads to bugs, some of which compromise security. This publication evaluates the types of vulnerabilities that can occur and leverages existing work on hardware weaknesses. For each type, a security failure scenario is provided that describes how the weakness could be exploited, where the weakness typically occurs, and what kind of damage could be done by an attacker."}], "metadata": {"source": "Hardware Security Failure Scenarios_ Potential Hardware Weaknesses", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Approaches for Federal Agencies to Use the Cybersecurity Framework:\n\n11 | AO | Authorizing Official | |-------|-------------------------------------------------------------------------------------------------------------------------------| | CI | Critical Infrastructure | | CIO | Chief Information Officer | | CISO | Chief Information Security Officer | | CNSS | Committee on National Security Systems | | EO | Executive Order | | FIPS | Federal Information Processing Standards | | FISMA | Federal Information Security Management Act of 2002, as amended, including the Federal Information Security Modernization Act | | HIPAA | Health Insurance Portability and Accountability Act | | HVA | High Value Asset | | ISCM | Information Security Continuous Monitoring | | ISO | International Organization for Standardization | | ITL | Information Technology Laboratory | | NIST | National Institute of Standards and Technology | | OMB | Office of Management and Budget | | POA&M | Plan of Action and Milestones | | RAR | Risk Assessment Report | | RFC | Request for Comment | | RFI | Request for Information | | RMF | Risk Management Framework | | SAR | Security Assessment Report | | SP | Special Publication | | SSP | System Security Plan |"}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Module-Lattice-Based Key-Encapsulation Mechanism Standard:\n\nBoth this standard and possible threats that reduce the security provided through the use of this standard will undergo review by NIST as appropriate, taking into account newly available analysis and technology. In addition, the awareness of any breakthrough in technology or any mathematical weakness of the algorithm will cause NIST to reevaluate this standard and provide necessary revisions."}], "metadata": {"source": "Module-Lattice-Based Key-Encapsulation Mechanism Standard", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Computer Security Division 2015 Annual Report:\n\nts biometric transactions based on NIST SP 500-290, and SP 500-290 Revision 1 - Data Format for the Interchange of Fingerprint, Facial & Other Biometric Information) received a substantial update.\nVersion 2.0 of the testing software was released and added support for testing for the remaining traditionally encoded record types not previously supported (+12 for ANSI/NIST-ITL 1-2011, and +18 for ANSI/NIST-ITL 1-2011 Update: 2013). Version 2.0 now supports all traditionally encoded biometric record types between the two versions of the published ANSI/NIST-ITL standards. Additionally, Version 2.0 added many enhanced editing features for traditionally encoded biometric transactions - some new features include: adding and removing records and fields, arranging records and fields, automatically sorting records, displaying the biometric sample image, and enhanced binary data editing features. In addition to the enhanced editing features, BioCTS for ANSI/NIST-ITL received many usability enhancements, as well as updates to some core software functionality, providing a more usable and robust testing tool."}], "metadata": {"source": "Computer Security Division 2015 Annual Report", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.6 (NIST 3.2.6)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.2.6) • Added optional capability to use the Global PIN (in addition to the PIV Card Application PIN) with the PIV Card Application (Part 1, Sec. 3.2.6) • Added pivMiddlewareVersion API function (SP 800-73-5 Part 3, Sec."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "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 guidance does Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions provide?"}, {"role": "assistant", "content": "\n\n## NIST Special Publication 800 NIST SP 800-232\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices\n\nAuthenticated Encryption, Hash, and Extendable Output Functions\n\nMeltem Sönmez Turan Kerry A. McKay Donghoon Chang Jinkeon Kang John Kelsey\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-232\n\n\n\n## NIST Special Publication 800 NIST SP 800-232\n\n## Ascon-Based Lightweight Cryptography Standards for Constrained Devices\n\nAuthenticated Encryption, Hash, and Extendable Output Functions\n\nMeltem Sönmez Turan Kerry A. McKay Jinkeon Kang* John Kelsey\n\nComputer Security Division Information Technology Laboratory\n\n* Former Foreign Guest Researcher; all work for this publication was done while at NIST. Donghoon Chang\n\nStrativia\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.SP.800-232\n\nAugust 2025\n\n\n\nU.S. Department of Commerce Howard Lutnick, Secretary\n\nCertain equipment, instruments, software, or materials, commercial or non-commercial, are identified in this paper in order to specify the experimental procedure adequately. Such identification does not imply recommendation or endorsement of any product or service by NIST, nor does it imply that the materials or equipment identified are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST."}], "metadata": {"source": "Ascon-Based Lightweight Cryptography Standards for Constrained Devices_ Authenticated Encryption, Hash, and Extendable Output Functions", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\n| Function | Category | | Subcategory |\n|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|\n| appropriate data processing safeguards. | and responsibilities in the data processing ecosystem, and management commitment), processes, and procedures are maintained and used to manage the protection of data. | PR.PO-P2: Configuration change control processes are established and in place."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Digital Identity Guidelines_ Identity Proofing and Enrollment provide? (Part 3)"}, {"role": "assistant", "content": "l official. This publication may be used by nongovernmental\norganizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST.\nNIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements\nNIST Technical Series Publication Identifier Syntax\n\n\fPublication History\n\nApproved by the NIST Editorial Review Board on 2025-05-30. Supersedes NIST SP 800-63A (June 2017; updated March 2, 2020) https://doi.org/10. 6028/NIST.SP.800-63a\n\nHow to Cite this NIST Technical Series Publication\n\nTemoshok D, Abruzzi C, Choong YY, Fenton JL, Galluzzo R, LaSalle C, Lefkovitz N,\nRegenscheid A, Vachino M (2025) Digital Identity Guidelines: Identity Proofing and\nEnrollment. (National Institute of Standards and Technology, Gaithersburg, MD), NIST\nSpecial Publication (SP) NIST SP 800-63A-4. https://doi.org/10.6028/NIST.SP.800-63A-4\n\nAuthor ORCID iDs\n\nDavid Temoshok: 0000-0001-6195-0331\nChristine Abruzzi: 0000-0001-8904-930X\nYee-Yin Choong: 0000-0002-3889-6047\nJames L. Fenton: 0000-0002-2344-4291\nRyan Galluzzo: 0000-0003-0304-4239\nConnie LaSalle: 0000-0001-6031-7550\nNaomi Lefkovitz: 0000-0003-3777-3106\nAndrew Regenscheid: 0000-0002-3930-527X\nMaria Vachino: 0000-0002-3494-5307\n\nContact Information\n\nmailto:dig-comments@nist.gov\n\nNational Institute of Standards and Technology\nAttn: Applied Cybersecurity Division, Information Technology Laboratory\n100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000\n\nAdditional Information\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/\nsp/800/63/A/4/final, including related content, potential updates, and document\nhistory. All comments are subject to release under the Freedom of Information Act (FOIA). NIST SP 800-63A-4\nJuly 2025\n\nAbstract\n\nDigital Identity Guidelines\nIdentity Proofing and Enrollment\n\nThis guideline focuses on identity proofing and enrollment for use in digital\nauthentication."}], "metadata": {"source": "Digital Identity Guidelines_ Identity Proofing and Enrollment", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Recommendations for Federal Vulnerability Disclosure Guidelines:\n\n3.2.2. 3.2.2."}], "metadata": {"source": "Recommendations for Federal Vulnerability Disclosure Guidelines", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Stateful Hash-Based Signature Schemes:\n\n| 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 | 1 Introduction ............................................................................................................1 |\n|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|\n| | 1.1 Intended Applications for Stateful HBS | Schemes........................................... 1 |\n| | 1.2 The Importance of the Proper Maintenance | of State ...................................... 1 |\n| | 1.3 Outline of Text | ................................................................................................"}], "metadata": {"source": "Recommendation for Stateful Hash-Based Signature Schemes", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Building a Cybersecurity and Privacy Learning Program:\n\nTeaching the workforce about different cybersecurity and privacy risks enables them to effectively address the risks they encounter in their daily activities. For example, all members of the workforce will need training that helps them understand what a privacy event is and how one might occur within their organization. They should be able to identify and report a privacy event. Incident response professionals will need training that helps them determine when a cybersecurity incident may also be a privacy event, which often requires additional procedures when responding (e.g., determining if an unsecured site resulted in an actual privacy breach). - Understanding how cybersecurity and privacy activities support the organization's mission and business objectives\n- Using proper passwords or multi-factor authentication\n- Handling data\n- Using AI or other enterprise tools\n- Learning remote access procedures\n- Collecting and protecting PII\n- Reporting any suspected incidents or violations of cybersecurity and privacy policies\n- Following the rules established to avoid social engineering attacks (e.g., ransomware and phishing) and to deter the spread of spam and malware\n- Identifying and addressing privacy risks during information processing\n- Knowing where to find the organization's cybersecurity and privacy resources and points of contact\n\n- New employees: This audience includes contractors, and the focus is usually on the important policies and rules of behavior for the systems that they will access. This training includes what is typically called 'new employee orientation' or 'onboarding' and can be joint cybersecurity and privacy training. Some organizations may need to require visitors and/or guests to sign acceptable use policies if they allow them any type of system access, including use of wireless network connections."}], "metadata": {"source": "Building a Cybersecurity and Privacy Learning Program", "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 Report of the Workshop on Cryptography in Support of Computer Security:\n\n## Report of the Workshop on Cryptography in Support of Computer Security\n\n## REPORT OF THE WORKSHOP ON CRYPTOGRAPHY IN SUPPORT OF COMPUTER SECURITY\n\nReport of the Workshop on Cryptography in Support of Computer Security"}], "metadata": {"source": "Report of the Workshop on Cryptography in Support 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 additional guidance does Recommendation for Key Management_ Part 1 – General provide? (Part 4)"}, {"role": "assistant", "content": "its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nThis Recommendation provides cryptographic key-management guidance. It consists of three parts.\nPart 1 provides general guidance and best practices for the management of cryptographic keying material, including definitions of the security services that may be provided when using cryptography and the algorithms and key types that may be employed, specifications of the protection that each type of key and other cryptographic information requires and methods for providing this protection, discussions about the functions involved in key management, and discussions about a variety of key-management issues to be addressed when using cryptography. Part 2 provides guidance on policy and security planning requirements for U.S. government agencies. Part 3 provides guidance when using the cryptographic features of current systems. ## Keywords\n\narchive; authentication; authorization; availability; backup; compromise; confidentiality; cryptographic key; cryptographic module; digital signature; hash function; key agreement; key management; key recovery; keying material; key transport; private key; public key; secret key; trust anchor. ## Acknowledgments\n\nThe National Institute of Standards and Technology (NIST) gratefully acknowledges and appreciates contributions by previous authors of this document on the many security issues associated with this Recommendation: William Barker, William Burr, and Timothy Polk from NIST; Miles Smid from Orion Security; and Lydia Zieglar from the National Security Agency. NIST also thanks the many contributions by the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication. NIST especially appreciates the comments submitted before, during, and after the public comment period by Paul Turner from Venafi."}], "metadata": {"source": "Recommendation for Key Management_ Part 1 – General", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio:\n\nSome weaknesses, such as software flaws or misconfigurations, can be identified using automated scanners. These automated techniques may help to quickly identify some common vulnerabilities, but ICT weaknesses are not limited to enterprise hardware and software. For the ICT risk disciplines of privacy, supply chain, and cybersecurity, reviewing the controls described in NIST SP 800-53, Security and Privacy Controls for Information Systems and Organizations , may help highlight many potential weaknesses [SP80053].\n\nOMB A-123 examples reference inherent risk that describes 'conditions in the absence of risk management actions.' There are often likely to be at least some elements that help mitigate risks, so this publication typically refers to current risk rather than inherent risk when representing a baseline risk posture."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Security of SQL-Based Implementations of Product Data Exchange Using STEP:\n\nThe basic SQL definition is ANSI X3. 135-1989, Database Language -SQL with Integrity Enhancement [ANS89a], and will be referred to as SQL'89. The functionality of SQL'89 includes schema definition, data manipulation, and transaction management. SQL'89 and ANSI X3. 168-1989, Database Language - Embedded SQL [ANS89b], form the basis for the Federal Information Processing Standard (FIPS) 127-1 [FIP90].\n\nSection 3 identifies controls and mechanisms that can be used to address the concerns described in Section 2. These controls are organized according to an augmented Trusted Computer System Evaluation Criteria (TCSEC) model presented in [PB93]. This model reflects the Trusted Database Interpretation (TDI) [TDI91] and National Computer Security Center (NCSC) Technical Report 79-91, Integrity In Automated Information Systems [TR791]. The Interpreted Requirements presented in the TDI provide the basis for discussions of labels and audit in database. Additions to the model from TR 79-91 include the definitions of data integrity and systems integrity.\n\nSTEP itself does not imply any particular implementation form or security policy. Certain policies are more easily implemented with the SQL/STEP architecture than others. In Section 4, three broad classes of security policies are briefly described, accompanied by a comparison of particular requirements with the facilities of SQL. The policy classes are: a role based policy, a mandatory access control policy for confidentiality, and a mandatory access control policy for integrity."}], "metadata": {"source": "Security of SQL-Based Implementations of Product Data Exchange Using STEP", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Science Challenges:\n\n3.2.2 | 3. 3.2.2 Correlation Between Cloud Technology and Forensic Science Challenges\n\nTo better understand the correlation between the cloud forensic science challenges and their cloud-based root cause, the NCC FSWG analyzed each challenge's relationship to the cloud functional capabilities (cloud processes or solutions) identified in the Cloud Security Alliance's (CSA's) Enterprise Architecture (EA) [9]and leveraged by the NIST Cloud Security Reference Architecture (CSRA) [10]."}], "metadata": {"source": "NIST Cloud Computing Forensic Science Challenges", "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 Risk Assessment?"}, {"role": "assistant", "content": "According to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\nThis publication can be used in conjunction with ISO/IEC/IEEE 15288:2015, Systems and\nsoftware engineering—Systems life cycle processes; NIST Special Publication (SP) 800-160,\nVolume 1, Systems Security Engineering—Considerations for a Multidisciplinary Approach in the\nEngineering of Trustworthy Secure Systems; NIST SP 800-37, Risk Management Framework for\nInformation Systems and Organizations—A System Life Cycle Approach for Security and Privacy;\nand NIST SP 800-53, Security and Privacy Controls for Information Systems and Organizations. It\ncan be viewed as a handbook for achieving the identified cyber resiliency outcomes based on a\nsystems engineering perspective on system life cycle and risk management processes, allowing\nthe experience and expertise of the implementing organization to help determine how the\ncontent will be used for its purpose. Organizations can select, adapt, and use some or all of the\ncyber resiliency constructs (i.e., goals, objectives, techniques, approaches, and design principles)\ndescribed in this publication and apply the constructs to the technical, operational, and threat\nenvironments for which systems need to be engineered. Advanced persistent threat; controls; cyber resiliency; cyber resiliency approaches; cyber\nresiliency design principles; cyber resiliency engineering framework; cyber resiliency goals; cyber\nresiliency objectives; cyber resiliency techniques; risk management strategy; system life cycle;\nsystems security engineering; trustworthiness. NIST SP 800-160, Volume 2, presents a cyber resiliency engineering framework to aid in\nunderstanding and applying cyber resiliency, a concept of use for the framework, and the\nengineering considerations for implementing cyber resiliency in the system life cycle. The\nframework constructs include goals, objectives, techniques, implementation approaches, and\ndesign principles."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Recommendations for Key-Encapsulation Mechanisms:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops tests,\ntest methods, reference data, proof of concept implementations, and technical analyses\nto advance the development and productive use of information technology. ITL’s respon-\nsibilities include the development of management, administrative, technical, and physical\nstandards and guidelines for the cost-effective security and privacy of other than national\nsecurity-related information in federal information systems. The Special Publication 800-\nseries reports on ITL’s research, guidelines, and outreach efforts in information system se-\ncurity, and its collaborative activities with industry, government, and academic organiza-\ntions.\n\ntermeasures (i.e., does not satisfy condition 2) or is deployed on a device with physical\nvulnerabilities (i.e., does not satisfy condition 3) is likely to be insecure in practice.\n\nCryptographic module implementation. The implementations of Π used by Alice\nand Bob need to satisfy the requirements in Sec. 3. Whether a given implemen-\ntation is sufficiently secure is an application-dependent question. For example, an\nimplementation might be secure enough for use on a web server in a physically se-\ncure location but have insufficient side-channel protections for use on an embedded\ndevice."}], "metadata": {"source": "Recommendations for Key-Encapsulation Mechanisms", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case provide? (Part 4)"}, {"role": "assistant", "content": "butions from individuals and organizations in the public and private sectors, whose thoughtful and constructive comments improved the overall quality, thoroughness, and usefulness of this publication.\nA special acknowledgement to the members of the ISA99, Industrial Automation and Control Systems Security Committee and the Department of Homeland Security Industrial Control System Joint Working Group (ICSJWG) for their exceptional contributions to this publication. ## Note to Readers\n\nThis guide describes a proof-of-concept solution for securing manufacturing environments that has only been tested in a lab environment. Manufacturers should make their own determinations about the breadth of the proof-of-concept solutions they voluntarily implement. Some important factors to consider include: company size, cybersecurity expertise, risk tolerance, and the threat landscape. We welcome feedback on its contents and your input. Comments, suggestions, and success stories will improve subsequent versions of this guide. Please contribute your thoughts to CSF\\_Manufacturing\\_Profile\\_Implementation@nist.gov. ## Revision to Include Updates in Cybersecurity Framework Version 1.1\n\nThe Cybersecurity Framework Manufacturing Profile, NISTIR 8183, was drafted and released when the Cybersecurity Framework was at Version 1.0. This guide provides implementation guidance and example proof-of-concept solutions with respect to the language in the original Cybersecurity Framework Manufacturing Profile. The Cybersecurity Framework Manufacturing Profile, NISTIR 8183, is scheduled to be revised to include the updates in the Cybersecurity Framework Version 1.1, and will be published as NISTIR 8183, Revision 1. Once NISTIR, 8183, Revision 1 has been released, this implementation guide will be revised to include the updates in the Cybersecurity Framework Version 1.1 as well, and will be published as NISTIR 8183A, Revision 1."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\n3.5.4 | Integration with Authentication ... 3.5.4 Integration with Authentication\n\nThe shift from internal to public-based hosting (e."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. HIPAA Security Rule .......................................................................................................................9 |\n| 3. Risk Assessment Guidance............................................................................................................14 |\n| 4. Risk Management Guidance .........................................................................................................24 |\n| 5. Considerations When Implementing the HIPAA Security Rule........................................................28 |\n| 5.1.2. Assigned Security Responsibility (§ 164.308(a)(2)) ....................................................................35 |\n| 5.1.3. Workforce Security (§ 164.308(a)(3)).........................................................................................36 |\n| 5.1.4. Information Access Management (§ 164.308(a)(4)) ..................................................................38 |\n| 5.1.5. Security Awareness and Training (§ 164.308(a)(5)) ...................................................................41 |\n| 5.1.6. Security Incident Procedures (§ 164.308(a)(6)) .........................................................................44 |\n| 5.1.7. Contingency Plan (§ 164.308(a)(7))............................................................................................47 |\n| 5.1.8."}], "metadata": {"source": "Implementing the Health Insurance Portability and Accountability Act (HIPAA) Security Rule_ A Cybersecurity Resource Guide", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Workshop on Enhancing Security of Devices and Components Across the Supply Chain:\n\nThe National Institute of Standards and Technology (NIST) hosted an in-person, all-day workshop on February 27, 2024, to discuss existing and emerging cybersecurity threats and mitigation techniques for semiconductors throughout their life cycle. The workshop obtained valuable feedback from industry, academia, and government to inform NIST's development of cybersecurity and supply chain standards, guidance, and recommended practices. The discussion focused on semiconductor development and highlighted cybersecurity measurements and metrics that utilize reference data sets to facilitate the testing, attestation, certification, verification, and validation of semiconductor components. It also emphasized the use of automated cybersecurity tools and techniques to secure manufacturing environments throughout the development life cycle. This report summarizes the content that was presented and discussed at the workshop. These activities range from physical protection mechanisms (e.g., tamper-resistant packaging) to strong encryption protocols to safeguard data. Secure boot processes ensure that only verified firmware runs, and maintaining supply chain integrity through verification and audits prevents counterfeit components. Life cycle management includes secure provisioning, updates, and end-of-life processes that are complemented by rigorous security testing and compliance with regulatory standards. Educating users on secure practices and continuously improving security measures further fortifies defenses against evolving threats and ensures that semiconductor devices operate securely throughout their life cycle. Furthermore, Jonathan stressed the importance and continued need for public-private partnerships, like the Semiconductor Research Corporation and the Semiconductor Industry Association."}], "metadata": {"source": "Workshop on Enhancing Security of Devices and Components Across the Supply Chain", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Cyber Threat Information Sharing:\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 securityrelated information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. Each organization should establish an information sharing plan that provides for ongoing infrastructure maintenance and user support. The plan should address the collection and analysis of threat information from both internal and external sources and the use of this information in the development and deployment of protective measures."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to IT Security for Industrial Control Systems:\n\nThe Process Control Security Requirements Forum (PCSRF) is a working group comprising representative organizations from the various sectors that make up the U.S. Process Control Industry and the vendors that design, produce, and/or integrate components and systems for the industry. The PCSRF is working with security professionals to assess the vulnerabilities and establish appropriate strategies for the development of policies and countermeasures that the U.S. process controls industry would employ through a combination IT and non-IT mechanisms to reduce residual risk to an acceptable level. The Common Criteria for Information Technology Security Evaluation, also known as ISO/IEC 15408. is being used to document the results of this effort in the form of Common Criteria Protection Profile security specifications. Primary focus area of the group to improve the IT security of the computer control systems used in process industries, including electric utilities, petroleum (oil & gas), water, waste, chemicals, pharmaceuticals, pulp & paper, and metals & mining with an emphasis on industries considered to be part of the Nation's Critical Infrastructure. The Common Criteria (CC), ISO/IEC 15408 [7], is a meta-standard of criteria and constructs used to develop security specifications in support of the evaluation of products and systems. The specifications define and characterize the security problem including assumptions about the operational environment, threats that must be encountered and policies that must be enforced. Also characterized is the intended approach to eliminate, minimize or monitor defined threats, and enforce stated policy. The specification defines functional requirements, specifying what the system is to do and assurance requirements, specifying what is done to verify that the system does exactly what it is supposed to. These CC requirements, selected from a catalog of criteria, are independent of technology and implementation."}], "metadata": {"source": "IT Security for Industrial Control Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Introduction to Cybersecurity for Commercial Satellite Operations:\n\nDesign and development. Is it important to have robust software and hardware design processes where developers add in security and perform proper security testing. Manufactures and companies should be aware of the long lifetime of some spacecraft and build in flexibility to address cyber threats over the lifetime of the vehicle. Specific attention should be placed on the cryptographic modules that may potentially allow for upgrades for post-quantum cryptography. Current operationally deployed systems should also consider using compensating controls to achieve outcomes if the legacy technologies are insufficient. The organization then generates a high-level cybersecurity risk model that can help identify its most severe cybersecurity vulnerabilities, the threat events that are most likely to occur, and events that could have the highest negative impact on the business. This analysis is less rigid than the detailed risk evaluation that occurs in Step 4 and is intended to spur discussion regarding the types of risk events that might have some impact on the organization. The resulting risk understanding helps shape the Current State Profile described in Step 3. | Functions | Subcategories | Informative SP 800-53, Rev. 4 | Reference SP 800-53, Rev."}], "metadata": {"source": "Introduction to Cybersecurity for Commercial Satellite Operations", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Research Report_ User Perceptions of Smart Home Privacy and Security:\n\nunderstanding of smart home device technology, functionalities, and privacy and security, there may be little meaningful mitigation actions being taken to protect consumer security and privacy [7-10].\n| Mitigation | # | Examples |\n|-----------------------------------|-----|------------------------------------------------------------------------------------------------------------------------------|\n| Authentication | 17 | setting or changing passwords on device apps, using facial recognition / biometrics |\n| Limiting audio and video exposure | 16 | not locating devices in certain rooms, restricting conversations when near devices, unplugging devices in certain situations |\n| Home network configuration | 14 | network segmentation, setting a Wi-Fi pass- word, using virtual private networks (VPNs) |\n| Configuring device options | 12 | disabling automatic ordering, history, and er- ror reporting |\n| Limiting information in apps | 8 | using fake information or infrequently-used email addresses |\n| Device selection | 7 | choosing devices with strong security / privacy features, buying products from trusted vendors |\n| Limiting access | 5 | limiting access to codes / passwords, placing orders from computer instead of from virtual assistant |\n| Updates | 3 | applying app and firmware updates, upgrading products |"}], "metadata": {"source": "Research Report_ User Perceptions of Smart Home Privacy and Security", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... |\n|--------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1.1 PURPOSEANDAPPLICABILITY | ................................................................................................... 3 |\n| 1.2 TARGET AUDIENCE | .................................................................................................................. 4 |\n| 1.3 ORGANIZATIONOF THIS SPECIAL PUBLICATION | .......................................................................... 4 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 | CHAPTERTWO THE FUNDAMENTALS............................................................................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................"}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U provide? (Part 2)"}, {"role": "assistant", "content": "ts, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\nOrganizations are encouraged to review all draft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity publications, other than the ones noted above, are available at https://csrc.nist.gov/publications. ## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST."}], "metadata": {"source": "Cryptographic Module Validation Program (CMVP)-Approved Sensitive Security Parameter Generation and Establishment Methods_ CMVP Validation Authority U", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 NIST Cloud Computing Forensic Reference Architecture:\n\nntracts and service-level agreements\n- o Issuing subpoenas without knowledge of the physical location of data\n8. Standards (e.g., standard operating procedures, interoperability, testing, validation).\nStandards challenges in cloud forensics include:\n- o Lack of minimum/basic SOPs, practices, and tools\n- o Lack of interoperability among cloud providers\n- o Lack of test and validation procedures\n9. Training (e.g., forensic investigators, cloud providers, qualification, certification). Training challenges in cloud forensics include:\n- o Misuse of digital forensic training materials that are not applicable to cloud forensics\n- o Lack of cloud forensic training and expertise for both investigators and instructors"}], "metadata": {"source": "NIST Cloud Computing Forensic Reference Architecture", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities provide?"}, {"role": "assistant", "content": "## NISTIR 8420B\n\n## The Federal Cybersecurity Awareness Workforce\n\nProfessional Backgrounds, Knowledge, Skills, and Development Activities\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420B\n\n\n\n## NISTIR 8420B\n\n## The Federal Cybersecurity Awareness Workforce\n\nProfessional Backgrounds, Knowledge, Skills, and Development Activities\n\nJulie Haney Jody Jacobs Susanne Furman Fernando Barrientos Information Access Division Information Technology Laboratory\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8420B\n\nMarch 2022\n\n\n\nU.S. Department of Commerce Gina M. Raimondo, Secretary\n\nNational Institute of Standards and Technology James K. Olthoff, Performing the Non-Exclusive Functions and Duties of the Under Secretary of Commerce for Standards and Technology & Director, National Institute of Standards and Technology\n\n## National Institute of Standards and Technology Interagency or Internal Report 8420B 36 pages (March 2022)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8420B\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "The Federal Cybersecurity Awareness Workforce_ Professional Backgrounds, Knowledge, Skills, and Development Activities", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. | 3.4.3. Enhancing Practices....................................................................................................................49 | |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|\n| 3.5.1. Measuring C-SCRM Through Performance Measures................................................................52 | |\n| References.........................................................................................................................................57 | |\n| Appendix A."}], "metadata": {"source": "Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Usability and Security Considerations for Public Safety Mobile Authentication:\n\nIn the United States over 10 000 jurisdictions employ public safety personnel to respond to emergency situations every day. These first responders treat life-threatening injuries, deal with the consequences of natural disasters, fight crime, and combat terrorism. To perform these duties, emergency responders must undergo unique training, utilize specialized equipment, and access a variety of information systems. The use of specialized tools, information systems, and protective equipment places first responders within a unique environment to perform their jobs. - Section 2, Usability of Authentication for Public Safety: Discusses why usability is critical for public safety, describes the usability research methodology, and explains qualitative data from public safety subject matter experts (SMEs). - Section 3, Fire Service, EMS, and Law Enforcement: Briefly describes Fire, EMS, and Law Enforcement, including specialized equipment for each. Discusses the current authentication practices for public safety personnel. - Section 4, Authentication Methods Under Review: Describes a variety of authentication methods under review within this analysis. - Section 5, Usability and Technical Considerations of Authentication Methods: Discusses the usability and technical considerations of authentication methods under review. In many cases, the considerations are similar across Fire, EMS, and Law Enforcement disciplines. - Section 6, Discussion and Future Directions: Summarizes the analysis of authentication methods for Fire, EMS, and Law Enforcement. Rates each method as impractical, challenging, or feasible for public safety. Discusses overarching concepts, potential mitigations, and identifies directions for future research. It is common to begin with qualitative research to understand users' characteristics, needs, tasks, and environments."}], "metadata": {"source": "Usability and Security Considerations for Public Safety Mobile Authentication", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Computer Security Division 2008 Annual Report:\n\n| Computer Security Division Publications - FY 2008 | 53 55 | | Ways to Engage Our Division and NIST | | | Acknowledgements | 56 |"}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "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 Glossary of Key Information Security Terms provide? (Part 4)"}, {"role": "assistant", "content": ", NIST Special Publications (SPs), and select NIST Internal or Interagency Reports (IRs), as well as from the Committee on National Security Systems Instruction 4009 (CNSSI-4009).\nThis repository ('the Glossary') contains two main parts: an online user interface application and an underlying database. The database, used as the foundation for the online application, contains terms and definitions extracted verbatim from NIST FIPS, SPs, and IRs, as well as from CNSSI4009. The online application was developed to allow users to search the database of terms and definitions. The Glossary is intended to help users understand terminology, recognize when and where multiple definitions may exist, and identify a definition that they can use. Over time, use of this Glossary will help standardize terms and definitions used, reducing confusion and the tendency to create unique definitions for different situations. This publication provides a broad overview of the Glossary's design. It describes the methodology, assumptions, and constraints used in the development of the underlying database and associated online user interface application (available at https://csrc.nist.gov/glossary). Specific implementation details are out of scope of this publication. This publication differs significantly from previous versions of NIST IR 7298. Previous versions contained a subset of basic terms that were most frequently used in NIST publications. This method was valuable, but greater demand and frequent updates to NIST's publication suite has necessitated the adoption of a more flexible solution. The audience for this publication also significantly differs from previous versions of NIST IR 7298."}], "metadata": {"source": "Glossary of Key Information Security Terms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Secure Virtual Network Configuration for Virtual Machine (VM) Protection provide? (Part 2)"}, {"role": "assistant", "content": "f 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.\nAttribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-125B Natl. Inst. Stand. Technol. Spec. Publ. 800-125B, 30 pages (March 2016) CODEN: NSPUE2\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-125B\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 http://csrc.nist.gov/publications."}], "metadata": {"source": "Secure Virtual Network Configuration for Virtual Machine (VM) Protection", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guidelines for Evaluating Differential Privacy Guarantees provide? (Part 5)"}, {"role": "assistant", "content": "| Differential Privacy Guarantee . | . . . . . . . . . . . . . . | 9 |\n| 2.1. | The Promise of Differential Privacy | . . . . . . . . . . .\n| 9 |\n| | 2.1.1. | The Math of Differential Privacy . . . . . . . . | 11 |\n| | 2.1.2. | Properties of Differential Privacy . . . . . . . . | 12 |\n| 2.2. | The Privacy Parameter ε . | . . . . . . . . . . . . . . . . | 13 |\n| 2.3. | Variants of Differential Privacy . | . . . . . . . . . . . . . | 16 |\n| 2.4. | The Unit of Privacy . . . . . . | . . . . . . . . . . . . . . | 20 |\n| | 2.4.1. | Bounded and Unbounded Differential Privacy | 20 |\n| | 2.4.2. | Defining One Person's Data . . . . . . . . . . . | 21 |\n| 2.5. | Comparing Differential Privacy Guarantees . | . . . . . . | 25 |\n| 2.6. | Mixing Differential Privacy With Other Data Releases . . . | Mixing Differential Privacy With Other Data Releases . . . | 27 |\n| 2.7. | Auditing and Empirical Measures of Privacy | . . . . . . | 28 |\n| 3. Differentially Private Algorithms . . . . . . . . | 3. Differentially Private Algorithms . . . . . . . . | . . . . . . . . | 29 |\n| 3.1. | Basic Mechanisms and Common Elements . | . . . . . . | 29 |\n| 3.2. | Utility and Accuracy . . . | . . . . . . . . . . . . . . . . . | 31 |\n| 3.3. | Bias . . . . . . . . . . . . . . . . . . | . . . . . . . . . . . | 35 |\n| | 3.3.1. | Systemic Bias . . . . . . . . . . . . . . . . . . . | 36 |\n| | 3.3.2. | Human Bias . . . . . . . . . . . . . . . . . . . . | 37 |\n| | 3.3.3. | Statistical Bias . . . . . . . . . . . . . . . . . ."}], "metadata": {"source": "Guidelines for Evaluating Differential Privacy Guarantees", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n| Executive Summary................................................................................................................. | Executive Summary................................................................................................................. | Executive Summary................................................................................................................. |\n|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|\n| | Introduction ...................................................................................................................... | 2 |\n| | Purpose...................................................................................................................... | 3 |\n| | Scope........................................................................................................................."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Computer Security Log Management:\n\narticularly for getting logs from key devices (e.g., firewalls and network intrusion detection systems that often transfer large amounts of log data) and for transferring log data between log servers.\nDuring a widespread malware incident or other network-based attack, regular networks might be unstable or unavailable. Another motivation for using a separate logging network is protecting log data on the organization's regular networks from eavesdropping. If a separate logging network is not used, logging communications on the regular network could be protected using additional security controls, such as data encryption. Another benefit of having a separate logging network is protecting those components that are only used for log management from attacks."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Cryptographic Key Generation:\n\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, MD), NIST Special Publication (SP) 800-38B, Includes updates as of October 06, 2016. https://doi.org/10.6028/NIST.SP.800-38B |\n|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\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, MD), NIST Special Publication (SP) 800-38F. 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, MD), NIST Special Publication (SP) 800-56A, Rev. 3. https://doi.org/10.6028/NIST.SP.800-56Ar3 |\n| SP 800-56B | Barker EB, Chen L, Roginsky A, Vassilev A, Davis R, Simon S (2019) Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography . (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) 800-56B, Rev. 2. https://doi.org/10.6028/NIST.SP.800-56Br2. |\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, MD), NIST Special Publication (SP) 800-56C, Rev. 1."}], "metadata": {"source": "Recommendation for Cryptographic Key Generation", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Approaches for Federal Agencies to Use the Cybersecurity Framework:\n\nOrganizations manage many types of risk. They develop policies to identify, assess, and mitigate adverse effects with cybersecurity dependencies across various types of enterprise risks. In addition to cybersecurity risks, other typical enterprise risks include safety, financial, program, acquisitions, supply chain, and privacy. Many of these other types of risk may also have cybersecurity risk implications or be impacted by cybersecurity. Some employ different terminologies and risk management approaches to make decisions. OMB Circular A-123 establishes an expectation for federal agencies to proactively consider and address risks through an integrated, organization-level view of events, conditions, or scenarios that impact mission achievement. Organizations may have established a unique lexicon for ERM that should be\n\nThe Cybersecurity Framework can be used to translate risk management practices and to support federal agencies as they interact with suppliers, including service providers, product vendors, systems integrators, organizations within a regulated sector, and other private sector partners.\n\nCybersecurity Framework Profile can be incorporated into the acquisition process as a foundation for evaluation criteria (agency), solicitation response (supplier), proposal/quote review (agency), minimum contract requirements (agency), contract compliance evidence (supplier), and contract compliance verification (agency). The use of Cybersecurity Framework Profiles allows suppliers the flexibility to select from among various standards and practices to"}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI):\n\n| 1 | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| | 1.1 APPLICABILITY, INTENDED AUDIENCE, AND USAGE ...................................................................3 | | | 1.2 CHANGES FOR THIS REVISION .....................................................................................................4 | | | 1.3 TIMELINES FOR USING THE REVISED GUIDELINES........................................................................4 | | | 1.4 KEY RELATED NIST PUBLICATIONS ...........................................................................................5 | | | 1.5 ORGANIZATION OF THIS SPECIAL PUBLICATION | ..........................................................................5 | | 2.PREPARATIONFORASSESSMENTANDAUTHORIZATION ......................................"}], "metadata": {"source": "Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for the Secure Deployment of IPv6 provide? (Part 5)"}, {"role": "assistant", "content": "| |\n| 2.\n| Document Structure ...............................................................................................1-1 | Document Structure ...............................................................................................1-1 | |\n| Introduction to IPv6....................................................................................................... | Introduction to IPv6....................................................................................................... | Introduction to IPv6......................................................................................................."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile:\n\nInclude cybersecurity considerations in the risk management strategy. Review and update the risk management strategy as determined necessary. Determine and allocate required resources to protect the manufacturing system. | 62443-2-1:2009 4.2.3.1, 4.2.3.3, 4.2.3.8, 4.2.3.9 PM-9, PM-11 |\n| IDENTIFY | Risk Assessment (ID.RA) | ID.RA-1 | Low and Moderate Develop a plan to identify, document, and report vulnerabilities that exist on the manufacturing system. Include the use of vulnerability scanning where safe and feasible on the manufacturing system, its components, or a representative system. Develop a plan for continuous monitoring of the security posture of the manufacturing system to facilitate ongoing awareness of vulnerabilities. Conduct risk assessments on the manufacturing system that take into account vulnerabilities and potential impact to manufacturing operations and assets. High Conduct performance/load testing and penetration testing on the manufacturing system with care | 62443-2-1:2009 4.2.3, 4.2.3.7, 4.2.3.9, 4.2.3.12 CA-2 CA-7 RA-3 |\n| IDENTIFY | Risk Assessment (ID.RA) | | to ensure that manufacturing operations are not adversely impacted by the testing process. Identify where manufacturing system vulnerabilities may be exposed to adversaries. Production systems may need to be taken off-line before testing can be conducted. If the manufacturing system is taken off-line for testing, tests are scheduled to occur during planned manufacturing outages whenever possible. If penetration testing is performed on non- manufacturing networks, extra care is taken to ensure that tests do not propagate into the manufacturing network. | CA-2(2), RA-5(4) |\n| IDENTIFY | Risk Assessment (ID.RA) | ID.RA-2 | Low and Moderate Establish and maintain ongoing contact with security groups and associations, and receive security alerts and advisories."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\nProfile | ........................................................................................\n3 |\n| | 1.3 | Audience......................................................................................................... 4 |\n| | 1.4 | Organization.................................................................................................... 4 |\n| 2 | Profile Basics...........................................................................................................6 | |\n| | 2.1 Profile Topics and Requirements, Augmentations, and Features | ..................."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "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 Cloud Computing Forensic Science Challenges provide?"}, {"role": "assistant", "content": "## NISTIR 8006\n\n## NIST Cloud Computing Forensic Science Challenges\n\nMartin Herman\n\nMichaela Iorga\n\nAhsen Michael Salim\n\nRobert H. Jackson\n\nMark R. Hurst\n\nRoss Leo\n\nRichard Lee\n\nNancy M. Landreville\n\nAnand Kumar Mishra\n\nYien Wang\n\nRodrigo Sardinas\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8006\n\n\n\n## NISTIR 8006\n\n## NIST Cloud Computing Forensic Science Challenges\n\n## Martin Herman\n\nInformation Access Division Information Technology Laboratory\n\n## Michaela Iorga\n\nComputer Security Division Information Technology Laboratory\n\nAhsen Michael Salim\n\nAmerican Data Technology, Inc. Research Triangle Park, NC\n\nRobert H. Jackson Mark R. Hurst SphereCom Enterprises Inc. Marshall, VA\n\nRoss Leo\n\nUniversity of Houston-Clear Lake CyberSecurity Institute Houston, TX\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8006\n\nAugust 2020\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology\n\nRichard Lee\n\nCitizens Financial Group Johnston, RI\n\n## Nancy M. Landreville\n\nMELE Associates (Germantown, MD) and Univ. of Maryland, GC (Adelphi, MD)\n\nAnand Kumar Mishra Malaviya National Institute of Technology Jaipur, India\n\nYien Wang Rodrigo Sardinas Auburn University\n\nAuburn, AL\n\n## National Institute of Standards and Technology Interagency or Internal Report 8006 87 pages (August 2020)\n\nThis publication is available free of charge from:\n\nhttps://doi.org/10.6028/NIST.IR.8006\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."}], "metadata": {"source": "NIST Cloud Computing Forensic Science Challenges", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to PIV Data Model Test Guidelines:\n\n## bytes shall identify the version number of that supplier's minutiae detection algorithm. AS05.02.07: The two most significant bytes of each of the two fields (\"Owner\" and \"Type\") of the CBEFF Product Identifier shall identify the vendor, and the two least significant\n\nused to sign the facial image e extended key usage extension. TE06.03.17.01: The tester shall validate that the certificate that was biometric data asserts the id-PIV-content-signing OID in th rtificate used to sign the biometrics shall be determined by the expiration of the card in accordance with Table 3-3 AS06.03.18: The size of the public key for digital signature ce of SP 800-78. | DTR from Section 6 | Test Assertion from Section 10 | DTR Description |\n|----------------------|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| TE06.03.07.02 | 10.3.1.13: Verify digital signature | s omitted, the tester shall validate that the certificate in the SignedData for the If the certificates field i CHUID can verify the digital signature in the SignerInfo. |\n| TE06.03.08.01 | 10.3.1.5: Verify crls field omission | om the SignedData. The tester shall validate that the crls field has been omitted fr |\n| TE06.03.09.01 | 10.3.1.6: Verify contents of signerInfos | The tester shall validate that only a single SignerInfo exists in the SignedData."}], "metadata": {"source": "PIV Data Model Test Guidelines", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms:\n\norchestration. A common desire is to only use cloud servers physically located within the same country as the organization, or physically located in the same country as the origin of the information.\nWhenever multiple container deployments are present on a single cloud server, there is a need to segregate those deployments from each other so that they do not interfere with each other, gain access to each other's sensitive data, or otherwise compromise the security or privacy of the containers. NIST IR 8320A, Hardware-Enabled Security: Container Platform Security Prototype [1] provides an overview of challenges organizations may face when using cloud-based container workloads, as well as techniques to improve the security of cloud computing and accelerate the adoption of cloud computing technologies by establishing an automated hardware root-of-trust method for enforcing and monitoring platform integrity and geolocation restrictions for cloud servers."}], "metadata": {"source": "Hardware-Enabled Security_ Policy-Based Governance in Trusted Container Platforms", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guide to Operational Technology (OT) Security:\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 concepts and\nmethodologies, may be used by federal agencies even before the completion of such companion publications. Thus,\nuntil each publication is completed, current requirements, guidelines, and procedures, where they exist, remain\noperative. For planning and transition purposes, federal agencies may wish to closely follow the development of\nthese new publications by NIST.\n\ncomputer security; distributed control systems (DCS); industrial control systems (ICS);\ninformation security; network security; operational technology (OT); programmable logic\ncontrollers (PLC); risk management; security controls; supervisory control and data acquisition\n(SCADA) systems.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and\nTechnology (NIST) promotes the U.S. economy and public welfare by providing technical\nleadership for the Nation’s measurement and standards infrastructure. ITL develops tests, test\nmethods, reference data, proof of concept implementations, and technical analyses to advance\nthe development and productive use of information technology. ITL’s responsibilities include the\ndevelopment of management, administrative, technical, and physical standards and guidelines for\nthe cost-effective security and privacy of other than national security-related information in\nfederal information systems. The Special Publication 800-series reports on ITL’s research,\nguidelines, and outreach efforts in information system security, and its collaborative activities\nwith industry, government, and academic organizations."}], "metadata": {"source": "Guide to Operational Technology (OT) 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 Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to Security Segmentation in a Small Manufacturing Environment:\n\nThroughout this paper, a fictional small manufacturer that operates a facility is used as an example. Figure 1 below shows a fictional company's assets and network. This diagram is representative of what may be found in a small manufacturing environment. In reality, manufacturing environments vary in complexity from this example.\n\nA security zone is a group of assets that have similar operational function and criticality; they share common cybersecurity requirements. Assets that have similar operational function often have similar system attributes and need similar protections; they may directly interact with each other and with the surrounding systems in a similar manner. The assets within the security zone have trusted communications with each other. Communication from inside a security zone to outside of the security zone is considered untrusted and subject to security controls. Security zones need to have physical or virtual boundaries to separate them from other security zones. A set of security practices that meets common security requirements is applied either at the security zone edge or within the security zone or both.\n\nSome possible security zones and sample assets within each security zone are listed below. A facility may not have all of these assets and some assets may be owned by the property manager, internet service provider (ISP), or other vendor. More security zone examples can be found in the six-step approach later in the document."}], "metadata": {"source": "Security Segmentation in a Small Manufacturing Environment", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Computer Security_ Selected Articles:\n\nment is in a position to lead the development of contingency plans for centralized data processing facilities. Because they must take the lead in contingency planning and in assuring the physical safety of the facilities under their immediate control, it does not follow that there is supporting rationale for the assignment to the DP area of responsibility for all data security. The people best equipped to mount the more sophisticated intrusions into the data processing complexes, who are most often described in the general and trade press as posing a major security threat because of their technical strength, report to the data processing management and are usually in the second and third salary quintiles. Contrary to conventional wisdom, these people are responsible for only a very small portion of employee theft through misuse of the data processing resources. To the extent that we have security problems presented by the technically strong employees, they usually do not involve theft but more commonly reflect £ desire to do harm to the organization as a result of morale problems of one type or another. There is a striking correlation between the amount of damage done by technically oriented data processing people and the imminence of such potentially disruptive events as mergers, acquisitions, and divestitures, which threaten the stability of the current DP organization This aspect of computer security, unlike the overall data secuny problem, is best controlled by the DP management to whom those people report. - Provide advice and consultation to the user community on computer security matters. - Maintain awareness of the state-of-the-art in computer security through professional organizations and peer contacts so as to bring early awareness to the DP staff and the users of significant developments in both security' measures and evolving problem categories. - Administer the access control package(s) which run on facilities under control of the DP organization."}], "metadata": {"source": "Computer Security_ Selected Articles", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n| 1. Introduction . . . . . . . . . . . . . | 1. Introduction . . . . . . . . . . . . . | 1. Introduction . . . . . . . . . . . . . |\n|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|\n| | 1.1. . . . . . . . . . . . . . . . | Notations . . . . . . . . . . . . . . . . . . . 1 |\n| | 1.1.1. Cryptographic Terminology . | . . . . . . . . . . . . . . . . . . . 2 |\n| 1.2. | Document Structure . . . . . . . . . | . . . . . . . . . . . . . . . . . . . 3 |\n| 2. Federation Assurance Level (FAL) . . . . . . . . . . . . . . . . . . . . . . . . 4 | 2. Federation Assurance Level (FAL) . . . . . . . . . . . . . . . . . . . . . . . . 4 | 2. Federation Assurance Level (FAL) . . . . . . . . . . . . . . . . . . . . . . . . 4 |\n| | 2.1. . . . . | Common FAL Requirements . . . . . . . . . . . . . . . . . . . . 5 |\n| | 2.2. | Federation Assurance Level 1 (FAL1) . . . . . . . . . . . . . . . . . . . . 6 |\n| | 2.3. | Federation Assurance Level 2 (FAL2) . . . . . . . . . . . . . . . . . . . . 6 |\n| | 2.4. | Federation Assurance Level 3 (FAL3) . . . . . . . . . . . . . . . . . . . . 7 |\n| 2.5."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Non-Fungible Token Security:\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": "Non-Fungible Token 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 does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\n| Function | Category | | Subcategory | |------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| | | Risk Assessment (ID.RA-P): The organization understands the privacy risks to individuals and how such privacy risks may create follow-on impacts on organizational operations, including mission, functions, other risk management priorities (e.g., compliance, financial), reputation, workforce, and culture."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters:\n\nwidely deployed technology can be used to safely expedite the transmission of voter registration and ballot request materials, as well as blank ballots. The same message may be provided to all voters.\nIn such cases, the information in the announcement is considered public information and therefore is not sensitive. This document will not discuss best practices for the distribution of these election information materials. However, ensuring the availability and reliability of the systems used to disseminate this information is important, and jurisdictions are directed to NISTIR 7682, Information System Security Best Practices for UOCAVA Supporting Systems [2], for information on security best practices to guard against accidental or malicious threats to system availability."}], "metadata": {"source": "Security Best Practices for the Electronic Transmission of Election Materials for UOCAVA Voters", "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 Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance:\n\npurposes that are shared by various Microsoft protocols and applications, and by other applications that may choose to use them. There is a similar 'Keychain' facility in the Apple operating systems.\nSome applications, intended to be portable between operating systems, can maintain their own root certificate stores and also have a feature that allows them to share a root certificate store with other applications. 6"}], "metadata": {"source": "Recommendation for Key Management, Part 3_ Application-Specific Key Management Guidance", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment:\n\n3.2.1 Plan Step... 3.2.1 Plan Step... 3.2.1 Plan Step\n\nThe Plan Step of the ISCM program assessment defines the assessment process and formalizes the conduct of a program assessment as illustrated in Figure 5."}], "metadata": {"source": "Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Protecting the Confidentiality of Personally Identifiable Information (PII):\n\nit does not know about. This document uses a broad definition of PII to identify as many potential sources of PII as possible (e.g., databases, shared network drives, backup tapes, contractor sites).\nPII is -any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual's identity, such as name, social security number, date and place of birth, mother's maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information.‖ 6 Examples of PII include, but are not limited to:"}], "metadata": {"source": "Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Cyber Threat Information Sharing:\n\nMany organizations handle information that, by regulation, law, or contractual obligation, requires protection. This includes PII, CUI, and other sensitive information afforded protection under the Sarbanes-Oxley Act (SOX), the Payment Card Industry Data Security Standard (PCI DSS), the Health Information Portability and Accountability Act (HIPAA), the Federal Information Security Modernization Act of 2014 (FISMA), and the Gramm-Leach-Bliley Act (GLBA) and other legislation, regulations, and guidelines. Organizations should identify and properly protect such information. An organization's legal team, privacy officers, auditors, and experts familiar with the various regulatory frameworks should be consulted when developing procedures for identifying and protecting sensitive information.\n\nOrganizations should establish policies and procedures that address the disposition of indicators (and threat information in general). Policies and procedures should define data retention requirements for short (online) and long (offline) term availability of indicator information. Information handling and retention requirements may change once threat information is entered into evidence. Evidence acquired during any incident investigations, for instance, should be collected and preserved using best practices for data preservation following chain of custody requirements and other laws pertaining to the submission of evidence. A more detailed treatment of forensic techniques related to chain of custody and preserving information integrity is available in NIST Special Publication 800-86 [12] and Section 3.3.2 of NIST Special Publication 800-61 [1].\n\nfixes the vulnerability, and the security operations team deploys logging and intrusion detection signatures to identify any similar future attacks."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Approaches for Federal Agencies to Use the Cybersecurity Framework:\n\nCybersecurity Framework Profile can be incorporated into the acquisition process as a foundation for evaluation criteria (agency), solicitation response (supplier), proposal/quote review (agency), minimum contract requirements (agency), contract compliance evidence (supplier), and contract compliance verification (agency). The use of Cybersecurity Framework Profiles allows suppliers the flexibility to select from among various standards and practices to\n\nUsing a Cybersecurity Framework Profile also may help identify opportunities for improving management of the organization's cybersecurity workforce and how it achieves defined risk tolerance outcomes. One way to do that is by applying the NICE Workforce Framework from the National Initiative for Cybersecurity Education (NICE), documented in SP 800-181 [13]. That workforce framework serves as a fundamental reference. It offers organizations a consistent lexicon for categorizing and describing cybersecurity work by category, specialty area, and work role, as well as a superset of cybersecurity knowledge, skills, and abilities (KSAs) and tasks for each work role. These elements support consistent organizational and sector communication for cybersecurity education, training, and workforce development. While the Cybersecurity Framework and the NICE Framework were developed separately, they complement each other by describing a hierarchical approach to achieving cybersecurity goals. The NICE program is in the process of determining alignment among Cybersecurity Framework subcategory outcomes and NICE Work Roles. As this work progresses, the alignment will help agencies document current and desired outcomes (based on Framework Core Subcategories) as well as the types of personnel that might have a role in accomplishing those outcomes."}], "metadata": {"source": "Approaches for Federal Agencies to Use the Cybersecurity Framework", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to Attribute Considerations for Access Control Systems:\n\n3.2.1 | Attribute Trustworthiness... 3.2.1 Attribute Trustworthiness\n\nAttribute trustworthiness considers how well the sources of attributes are authenticated, identified, and validated. 3.2.1."}], "metadata": {"source": "Attribute Considerations for Access Control Systems", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Information Security Guide for Government Executives:\n\nul, executives need to understand how to systematically recognize and address information security risks and take steps to understand and manage these risks through their information security program.\nInformation and information systems serve as a fundamental enabler for Federal agencies to meet their primary objective of serving the American public-making the confidentiality, integrity, and availability of information paramount to the Federal government's ability to deliver services to the American public. Information security should be closely aligned with business or mission goals. The cost of protecting information and information assets should not exceed the value of the assets. To properly align business risks and information security, management should facilitate a cooperative discussion between business units and information security managers."}], "metadata": {"source": "Information Security Guide for Government Executives", "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 Communications Protection?"}, {"role": "assistant", "content": "According to COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0:\n\nThe TOE will provide user services directly or serve as a platform for networked applications and will support protected communications across an untrusted network.\n\nFDP\\_ACC.1.1 The TSF shall enforce the [ assignment: CSPP access control SFP] on [ assignment: all subjects, all operating system controlled files (to include all communications mechanisms - for internal or external communications - that are implemented as objects controlled by the file system), and all access requests to these files].\n\nFPT\\_RPL.1.1-CSPP The TSF shall detect replay for the following entities [ extension: security state information that is critical to maintaining a secure state among distributed systems as identified in [ ST assignment: list of TSF data requiring such protection] ]. The ST rationale shall provide a basic justification, showing that the ST assignment is complete. It is acceptable to protect all communications, rather than selecting specific entities."}], "metadata": {"source": "COTS Security Protection Profile - Operating Systems (CSPP-OS) (Worked Example Applying Guidance of NISTIR-6462, CSPP) Version 1.0", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Information Security Guide for Government Executives:\n\n| Information Security Program Elements | Information Security Program Elements | |-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Awareness and Training | The security awareness and training program is a critical component of the information security program."}], "metadata": {"source": "Information Security Guide for Government Executives", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. - Hard copy. Hard copy media refers to physical representations of information, typically paper printouts, film, microfiche, etc. However, printer and facsimile ribbons, drums, and platens are also examples of hard copy media. The supplies associated with producing paper printouts are often the most uncontrolled. Hard copy materials containing sensitive data that leave an organization without effective sanitization expose a significant vulnerability to 'dumpster divers' and overcurious employees. - Information storage media (ISM)."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Bluetooth Security:\n\nSeveral Bluetooth versions are currently in use in commercial devices, while the most current version can be found at bluetooth.com. At the time of writing, Bluetooth 4.0 (adopted June 2010) is the most prevalent. The most recent versions include Bluetooth 4.1 and Bluetooth 4.2. Bluetooth 4.1 (adopted December 2013) improved the strengths of the Basic Rate/Enhanced Data Rate (BR/EDR) technology cryptographic key, device authentication, and encryption by making use of Federal Information Processing Standard (FIPS)-approved algorithms. Bluetooth 4.2 (adopted December 2014) improved the strength of the low energy technology cryptographic key by making use of FIPS-approved algorithms, and provided means to convert BR/EDR technology keys to low energy technology keys and vice versa. This publication addresses the security of all versions of Bluetooth. most secure, and for Bluetooth 2.0 and older devices Security Mode 3 is recommended. Security Modes 2 and 4 can also use authentication and encryption, but do not initiate them until after the Bluetooth physical link has already been fully established and logical channels partially established. Security Mode 1 devices never initiate security and therefore should never be used."}], "metadata": {"source": "Guide to Bluetooth Security", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices provide? (Part 4)"}, {"role": "assistant", "content": "ors also gratefully acknowledge and appreciate the many comments from the public and private sectors whose thoughtful and constructive comments improved the quality and usefulness of this publication.\n## Note\n\nNIST Special Publication (SP) 800-60 may be used by organizations in conjunction with a family of security-related publications including:\n\n- FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems;\n- FIPS Publication 200, Minimum Security Controls for Federal Information Systems ;\n- NIST SP 800-30, Risk Management Guide for Information Technology Systems 1 ;\n- NIST SP 800-37, Guide for the Security Certification and Accreditation of Federal Information Systems;\n- NIST Draft SP 800-39, Managing Risk from Information Systems: An Organizational Perspective;\n- NIST SP 800-53, Recommended Security Controls for Federal Information Systems;\n- NIST SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems ; and\n- NIST SP 800-59, Guideline for Identifying an Information System as a National Security System . This series of nine documents is intended to provide a structured, yet flexible framework for selecting, specifying, employing, and evaluating the security controls in Federal information systems-and thus, make a significant contribution toward satisfying the requirements of the Federal Information Security Management Act (FISMA) of 2002. While the publications are mutually reinforcing and have some dependencies, in most cases, they can be effectively used independently of one another. This is Volume II of two volumes. Volume I contains the basic guidelines for mapping types of information and information systems to security categories. The appendices contained in Volume II include security categorization recommendations and rationale for mission-based and management and support information types."}], "metadata": {"source": "Guide for Mapping Types of Information and Information Systems to Security Categories_ Appendices", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC:\n\n| Table of Contents | Table of Contents | Table of Contents | Table of Contents | |-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | PURPOSE...........................................................................................................................................................1 | PURPOSE...........................................................................................................................................................1 | PURPOSE...........................................................................................................................................................1 | | 2 | AUTHORITY.....................................................................................................................................................1 | AUTHORITY.....................................................................................................................................................1 | AUTHORITY.....................................................................................................................................................1 | | 3 | INTRODUCTION..............................................................................................................................................1 | INTRODUCTION..............................................................................................................................................1 | INTRODUCTION..............................................................................................................................................1 | | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | | 4.1 | 4.1 | DEFINITIONS AND ABBREVIATIONS .............................................................................................................2 | | | 4.2 | 4.2 | SYMBOLS ....................................................................................................................................................5 | | | 4.2.1 | 4.2.1 | Variables................................................................................................................................................5 | | | 4.2.2 | 4.2.2 | Operations and Functions .....................................................................................................................6 | | | 5 ELEMENTS OF GCM......................................................................................................................................7 | 5 ELEMENTS OF GCM......................................................................................................................................7 | 5 ELEMENTS OF GCM......................................................................................................................................7 | | | 5.1 | 5.1 | BLOCK CIPHER ............................................................................................................................................7 | | | 5.2 | 5.2 | TWO GCMFUNCTIONS ...............................................................................................................................7 | | | 5.2.1 | 5.2.1 | Authenticated Encryption Function .......................................................................................................8 | | | 5.2.2 | 5.2.2 | Authenticated Decryption Function.......................................................................................................9 | | | 5.3 | 5.3 | PRIMITIVES FOR CONFIDENTIALITY AND AUTHENTICATION........................................................................9 | | | 6 MATHEMATICAL COMPONENTS OF GCM...........................................................................................10 | 6 MATHEMATICAL COMPONENTS OF GCM...........................................................................................10 | 6 MATHEMATICAL COMPONENTS OF GCM...........................................................................................10 | | |"}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC", "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 Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\n- Compromising the software development toolchain (e.g., compilers, linkers, interpreters,\ncontinuous integration tools, code repositories). This allows malicious code to be inserted by\nthe adversary without modifying the source code or without the knowledge of the software\ndevelopers.\n\nCyber resiliency is based on the recognition that adversaries can establish and maintain a covert\npresence in systems. Therefore, many cyber resiliency techniques and approaches are not\npredicated on the assumption of successfully detecting adversity, including cyber-attacks. These\ninclude the Coordinated Protection, Deception, Diversity, Non-Persistence, Realignment,\nRedundancy, Substantiated Integrity, and Unpredictability techniques, and the Fragmentation,\nDistributed Functionality, Predefined Segmentation, Attribute-Based Usage Restriction, and\nTrust-Based Privilege Management approaches.\n\nTwo cyber resiliency techniques directly involve the detection of adversity or its effects: Analytic\nMonitoring and Contextual Awareness. The Substantiated Integrity technique and the\nConsistency Analysis approach support detection of some effects of adversity."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case provide?"}, {"role": "assistant", "content": "## NISTIR 8183A Volume 3\n\n## Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide:\n\nVolume 3 -Discrete-based Manufacturing System Use Case\n\nKeith Stouffer Timothy Zimmerman CheeYee Tang Jeffrey Cichonski Michael Pease Neeraj Shah Wesley Downard\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8183A-3\n\n\n\n## NISTIR 8183A Volume 3\n\n## Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide:\n\nVolume 3 -Discrete-based Manufacturing System Use Case\n\nKeith Stouffer Timothy Zimmerman CheeYee Tang Michael Pease Intelligent Systems Division Engineering Laboratory\n\nNeeraj Shah Strativia, LLC Largo, Maryland\n\nJeffrey Cichonski Applied Cybersecurity Division Information Technology Laboratory\n\nWesley Downard G2, Inc. Annapolis Junction, Maryland\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8183A-3\n\nSeptember 2019\n\n\n\nU.S. Department of Commerce Wilbur L. Ross, Jr., Secretary\n\nNational Institute of Standards and Technology\n\nWalter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology\n\n## National Institute of Standards and Technology Internal Report 8183A, Volume 3 296 pages (September 2019)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8183A-3\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."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 3 – Discrete-based Manufacturing System Use Case", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guide to Attribute Based Access Control (ABAC) Definition and Considerations:\n\n| Audience .........................................................................................................................\n| Audience ......................................................................................................................... | 1 |\n| 1.3 | Document Structure ...................................................................................................... | Document Structure ...................................................................................................... | 1 |\n| 1.4 | Notes on Terminology ................................................................................................... | Notes on Terminology ................................................................................................... | 2 |\n| 2. Understanding ABAC .......................................................................................................... | 2. Understanding ABAC .......................................................................................................... | 2. Understanding ABAC .......................................................................................................... | 4 |\n| 2.1 The Benefit of ABAC ..................................................................................................... | 2.1 The Benefit of ABAC ..................................................................................................... | 2.1 The Benefit of ABAC ....................................................................................................."}], "metadata": {"source": "Guide to Attribute Based Access Control (ABAC) Definition and Considerations", "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 Glossary of Key Information Security Terms provide? (Part 3)"}, {"role": "assistant", "content": "tems. ## Abstract\n\nThis publication describes an online glossary of terms used in National Institute of Standards and Technology (NIST) and Committee on National Security Systems (CNSS) publications.\nThis glossary utilizes a database of terms extracted from NIST Federal Information Processing Standard Publications (FIPS), the NIST Special Publication (SP) 800 series, select NIST Interagency or Internal Reports (NISTIRs), and from the Committee for National Security Systems Instruction 4009 (CNSSI-4009). ## Keywords\n\ncybersecurity; definitions; glossary; information assurance; information security; terminology. ## Supplemental Content\n\nThe online glossary described in this publication is publicly available at https://csrc.nist.gov/glossary. ## Table of Contents\n\n| 1 | Introduction ............................................................................................................1 |\n|-----|------------------------------------------------------------------------------------------------------------------------------|\n| 2 | Methodology...........................................................................................................2 |\n| 2.2 | Data ................................................................................................................ 3 |\n| 2.3 | Web Application.............................................................................................. 4 |\n\n## 1 Introduction\n\nThe National Institute of Standards and Technology (NIST) has created an easily-accessible repository of terms and definitions extracted verbatim from NIST Federal Information Processing Standard Publications (FIPS), NIST Special Publications (SPs), and select NIST Internal or Interagency Reports (IRs), as well as from the Committee on National Security Systems Instruction 4009 (CNSSI-4009)."}], "metadata": {"source": "Glossary of Key Information Security Terms", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guidelines for API Protection for Cloud-Native Systems:\n\nAnother distinguishing feature of the controls recommended for protecting APIs is the capacity to provide assurance for conforming to the principles of zero trust. This is because there is no distinction between internal and external API requests or calls due to the absence of an identifiable network perimeter and the distributed nature of applications on-premises and in multiple clouds. This security assurance can be achieved with authentication and authorization controls using identity-based segmentation [2]. Documents that provide recommendations on the configuration of authentication and authorization controls in the context of cloud-native applications (e.g., [2][3]) are also relevant in the context of configuring controls for API protection.\n\n- Missing authentication (e.g., tokens can be present but simply not checked), often due to a bug or misconfiguration in the application\n- Weak or predictable tokens, default accounts, and default passwords (e.g., a hard-coded bootstrap account with the same username and password on all devices, test accounts with predictable names and weak/guessable passwords)\n\nFor runtime protections for APIs, apply zero trust principles as a baseline, and augment them with additional policy on requests and their payloads."}], "metadata": {"source": "Guidelines for API Protection for Cloud-Native Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Information Security Handbook_ A Guide for Managers:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology 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 nonnational-security-related information in federal information systems. This Special Publication 800 series reports on ITL's research, guidelines, and outreach efforts in information system security and its collaborative activities with industry, government, and academic organizations. - The Federal Information Security Management (FISMA) Act is the primary legislation governing federal information security programs, building upon earlier legislation through added emphasis on the management dimension of information security. - -FISMA delegates to the National Institute of Standards and Technology (NIST) the responsibility to develop detailed information security standards and guidance for federal information systems, with the exception of national security systems. - -FISMA designates to OMB the oversight of federal agencies' information security implementation. - -FISMA provides a comprehensive framework for securing federal government IT resources, including defining key federal government and agency roles and responsibilities, requiring agencies to integrate information security into their capital planning and enterprise architecture processes, requiring agencies to conduct annual information security reviews of all programs and systems, and reporting the results of those reviews to OMB."}], "metadata": {"source": "Information Security Handbook_ A Guide for Managers", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Service Mesh Proxy Models for Cloud-Native Applications:\n\nAdditional information about this publication is available at https://csrc.nist.gov/pubs/sp/800/233/final, including related content, potential updates, and document history. | October 2024 | October 2024 | Cloud-Native Applications |\n|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|\n| 5.2.7. | Denial of Service (TR-7)...........................................................................................................19 | |\n| 5.2.8."}], "metadata": {"source": "Service Mesh Proxy Models for Cloud-Native Applications", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Enhanced Security Requirements for Controlled Unclassified Information:\n\n| CHAPTERONE INTRODUCTION...................................................................................................... | CHAPTERONE INTRODUCTION...................................................................................................... | 1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----|\n| 1.1 | PURPOSEANDAPPLICABILITY............................................................................................................. 1 | 2 |\n| 1.2 | TARGET AUDIENCE.............................................................................................................................. | |\n| 1.3 | ORGANIZATIONOF THIS SPECIAL PUBLICATION................................................................................. | 2 |\n| CHAPTERTWO THE FUNDAMENTALS............................................................................................ | CHAPTERTWO THE FUNDAMENTALS............................................................................................ | 3 |\n| 2.1 | ASSESSMENT PROCEDURES................................................................................................................"}], "metadata": {"source": "Assessing Enhanced Security Requirements for Controlled Unclassified Information", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide for Conducting Risk Assessments:\n\nfeguards and/or countermeasures (i.e., security controls), in which adversaries change some characteristic of their intent/targeting in order to avoid and/or overcome those safeguards/countermeasures.\nThreat shifting can occur in one or more domains including: (i) the time domain (e.g., a delay in an attack or illegal entry to conduct additional surveillance); (ii) the target domain (e.g., selecting a different target that is not as well protected); (iii) the resource domain (e.g., adding resources to the attack in order to reduce uncertainty or overcome safeguards and/or countermeasures); or (iv) the attack planning/attack method domain (e.g., changing the attack weapon or attack path). Threat shifting is a natural consequence of a dynamic set of interactions between threat sources and types of organizational assets targeted. With more sophisticated threat sources, it also tends to default to the path of least resistance to exploit particular vulnerabilities, and the responses are not always predictable. In addition to the safeguards and/or countermeasures implemented and the impact of a successful exploit of an organizational vulnerability, another influence on threat shifting is the benefit to the attacker. That perceived benefit on the attacker side can also influence how much and when threat shifting occurs."}], "metadata": {"source": "Guide for Conducting Risk Assessments", "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 Recommendation for Existing Application-Specific Key Derivation Functions:\n\n| | 3. The computation of a digital signature from data, 4. The verification of a digital signature, 5. The computation of an authentication code from data, 6. The verification of an authentication code from data and a received authentication code. |\n|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Key agreement primitive | A DLC primitive specified in SP 800-56A [SP 800-56A] or an RSA Secret Value Encapsulation (RSASVE) operation specified in SP 800-56B [SP 800-56B]. |\n| Key derivation key | A key that is used as an input to a key derivation function or key expansion function to derive other keys. |\n| Nonce | A time-varying value that has at most a negligible chance of repeating; for example, a random value that is generated anew for each use, a time-stamp, a sequence number, or some combination of these. It can be a secret or non-secret value. |\n| Pre-shared key | A secret key that is established between communicating parties before a communication protocol starts. |\n| Pseudorandom function (PRF) | A function that can be used to generate output from a random seed and a data variable, such that the output is computationally indistinguishable from truly random output. |\n| Pseudorandom key | As used in this Recommendation, a binary string that is taken from the output of a PRF. |\n| Secret keying material | The binary data that is used to form secret keys, such as AES encryption keys or HMAC keys. |\n| Shall | This term is used to indicate a requirement that needs to be fulfilled to claim conformance to this Recommendation. Note that shall may be coupled with not to become shall not."}], "metadata": {"source": "Recommendation for Existing Application-Specific Key Derivation 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 additional guidance does Risk Management for Replication Devices provide? (Part 3)"}, {"role": "assistant", "content": "xploits; mitigation; multifunction devices; printers; replication devices; risk; risk assessment; risk management; scanners; security controls; System Development Life Cycle; threats; vulnerabilities.\n## Table of Contents\n\n| Table of Contents......................................................................................................................................... iv |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction .............................................................................................................................................. 1 |\n| 1.1 Background.......................................................................................................................................... 1 |\n| 1.2 Purpose and Applicability ................................................................................................................... 1 |\n| 1.3 Target Audience................................................................................................................................... 2 |\n| 1.4 Document Structure............................................................................................................................. 2 |\n| 2. Threats and Vulnerabilities ..................................................................................................................... 3 |\n| 2.1 General Threats and Vulnerabilities ................................................................................................... 3 |\n| 2.2 Network Connectivity Threats and Vulnerabilities .............................................................................."}], "metadata": {"source": "Risk Management for Replication Devices", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Security of SQL-Based Implementations of Product Data Exchange Using STEP provide? (Part 4)"}, {"role": "assistant", "content": "six IRs and two APs. Note that PDES is not a standard. PDES stands for Product Data Exchange Using STEP. PDES 'refers to the United States contributing effort to this standardization process' [FCF93].\n## 1.3 Using This Document\n\nThis paper will be most useful to people who are familiar with SQL or relational database management systems. The reader is also assumed to have a basic knowledge of computer security or to have previously read [PB93]. Finally, the document also assumes some familiarity with STEP, although it is not required. SQL is a general purpose tool that could be used to implement STEP in various ways. Section 2, SQL/STEP Architecture, presents a basic architecture for an SQL-based implementation of STEP. This section examines security considerations that are of increased importance for this architecture. Section 3 identifies controls and mechanisms that can be used to address the concerns described in Section 2. These controls are organized according to an augmented Trusted Computer System Evaluation Criteria (TCSEC) model presented in [PB93]. This model reflects the Trusted Database Interpretation (TDI) [TDI91] and National Computer Security Center (NCSC) Technical Report 79-91, Integrity In Automated Information Systems [TR791]. The Interpreted Requirements presented in the TDI provide the basis for discussions of labels and audit in database. Additions to the model from TR 79-91 include the definitions of data integrity and systems integrity. STEP itself does not imply any particular implementation form or security policy. Certain policies are more easily implemented with the SQL/STEP architecture than others. In Section 4, three broad classes of security policies are briefly described, accompanied by a comparison of particular requirements with the facilities of SQL. The policy classes are: a role based policy, a mandatory access control policy for confidentiality, and a mandatory access control policy for integrity."}], "metadata": {"source": "Security of SQL-Based Implementations of Product Data Exchange Using STEP", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Trustworthy Email:\n\n�is document gives recommendations and guidelines for enhancing trust in email . �e primary audience includes enterprise email administra tors, information security specialists and network managers. �is guideline applies to federal IT systems and will also be useful for small or medium sized organizations. Technologies recommended in support of core Simple Mail Transfer Protocol (SMTP) and the Domain Name System (DNS) include mechanisms for authenticating a sending domain: Sender Policy Framework (SPF), Domain Keys Identified Mail (DKIM) and Domain based Message Authentication, Reporting and Conformance (DMARC). Recommendations for email transmission security include Transport Layer Security (TLS) and associated certificate authentication protocols. Recommendations for email content security include the encryption and authentication of message content using S/MIME (Secure/Multipurpose Internet Mail Extensions) and associated certificate and key distribution protocols.\n\nEmail; Simple Mail Transfer Protocol (SMTP); Transport Layer Security (TLS); Sender Policy Framework (SPF); Domain Keys Identified Mail (DKIM); Domain based Message Authentication, Reporting and Conformance (DMARC); Authentication of Named Entities (DANE); S/MIME; OpenPGP.\n\n�e Internet's underlying core email protocol, Simple Mail Transport Protocol (SMTP), was first adopted in 1982 and is still deployed and operated today. However, this protocol is susceptible to a wide range of attacks including man -in-themiddle content modification and content surveillance. �e basic standards have been modified and augmented over the years with adaptations that mitigate some of these threats. With spoofing protection, integrity protection, encryption and authentication, properly implemented email systems can be regarded as sufficiently secure for governme nt, financial and medical communications."}], "metadata": {"source": "Trustworthy Email", "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 Media Protection?"}, {"role": "assistant", "content": "According to Service Mesh Proxy Models for Cloud-Native Applications:\n\n| October 2024 | October 2024 | Cloud-Native Applications |\n|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|\n| 5.2.7. | Denial of Service (TR-7)...........................................................................................................19 | |\n| 5.2.8."}], "metadata": {"source": "Service Mesh Proxy Models for Cloud-Native Applications", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry:\n\nIn today's highly connected, interdependent world, all organizations rely on others for critical products and services. However, the reality of globalization, while providing many benefits, has resulted in a world where organizations no longer fully control-and often do not have full visibility into-the supply ecosystems of the products that they make or the services that they deliver. With more and more businesses becoming digital, producing digital products and services, and moving their workloads to the cloud, the impact of a cybersecurity event today is greater than ever before and could include personal data loss, significant financial losses, compromise of product integrity or safety, and even loss of life. Organizations can no longer protect themselves by simply securing their own infrastructures since their electronic perimeter is no longer meaningful; threat actors intentionally target the suppliers of more cyber-mature organizations to take advantage of the weakest link. Cybersecurity risks associated with this loss of control (and visibility) can be significant. They range from unknown provenance of hardware or software that supports an organization's digital functions to subcontractors and consultants having access to its critical data. This phenomenon is referred to as cybersecurity aspects of C-SCRM. Over the last decade, C-SCRM has evolved from a narrow focus on information and communication technology (ICT) supply chains to covering any cybersecurity-related supply chain risk. Today, it encompasses an increasing array of digital products and services that continues to grow with the expanding role of cyber space in the daily lives of individuals and in how business is conducted."}], "metadata": {"source": "Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\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. In today's cloud data centers and edge computing, attack surfaces have shifted and, in some cases, significantly increased. At the same time, hacking has become industrialized, and most security control implementations are not coherent or consistent. The foundation of any data center or edge computing security strategy should be securing the platform on which data and workloads will be executed and accessed. The physical platform represents the first layer for any layered security approach and provides the initial protections to help ensure that higher-layer security controls can be trusted. This report explains hardware-enabled security techniques and technologies that can improve platform security and data protection for cloud data centers and edge computing. In the scope of this document, the hardware platform is a server (e.g., application server, storage server, virtualization server) in a data center or edge compute facility. The server's hardware platform, also called the server platform , represents the first part of the layered security approach. Hardware-enabled security -security with its basis in the hardware platform-can provide a stronger foundation than one offered by software or firmware, which has a larger attack surface and can be modified with relative ease."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nthe Federal Information Security Modernization Act of 2014 (FISMA), the Privacy Act of 1974, OMB policies, and Federal Information Processing Standards, among other laws, regulations, and policies.\nThe scope of this publication pertains to federal information systems, which are discrete sets of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information, whether such information is in digital or non-digital form. Information resources include information and related resources, such as personnel, equipment, funds, and information technology."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Configuration Management?"}, {"role": "assistant", "content": "According to Computer Security Division 2009 Annual Report:\n\n- Issued sixteen NIST Special Publications (SP) covering management, operational, and technical security guidance, as well as four NIST Interagency Reports (NISTIRs) on technical topics, and one revised Federal Information Processing Standard (FIPS);\n- Collaborated with the Office of the Director of National Intelligence, Committee on National Security Systems, and the Department of Defense to establish a common foundation for information security across the federal government, including a consistent process for selecting and specifying safeguards and countermeasures (i.e., security controls) for federal information systems;\n- Provided assistance to agencies and private sector. Conducted ongoing, substantial reimbursable and non-reimbursable assistance support, including many outreach efforts such as the Federal Information Systems Security Educators' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSPM Forum), and the Small Business Corner;\n- o Drafted NISTIR 7621, Small Business Information Security: The Fundamentals , which was released in August 2009. NISTIR 7621 helps small businesses and other small organizations implement the fundamental components of an effective information security program;\n- o Initiated the development of an outreach video for the Small Business Outreach to help promote Information Technology (IT) security awareness for small to medium sized businesses. This video is expected to be publicly available in October 2009 on the CSRC website;\n- Evaluated security policies and technologies from the private sector and national security systems for potential federal agency use. Assembled a growing repository of federal agency security practices, public/private security practices, and security configuration checklists for IT products."}], "metadata": {"source": "Computer Security Division 2009 Annual Report", "cmmc_level": "2", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n---------------------------------------|\n| IDENTIFY | Asset Management (ID.AM) | ID.AM-1 | Low Impact Document an inventory of manufacturing system components that reflects the current system.\nManufacturing system components include for example PLCs, sensors, actuators, robots, machine tools, firmware, network switches, routers, power supplies, and other networked components or devices. System component inventory is reviewed and updated as defined by the organization. Information deemed necessary for effective accountability of manufacturing system components includes, for example, hardware inventory specifications, component owners, networked components or devices, machine names and network addresses. Inventory specifications include, for example, manufacturer, device type, model, serial number, and physical location. | ISA/IEC 62443-2- 1:2009 4.2.3.4 ISA/IEC 62443-3- 3:2013 SR 7.8 CM-8 |\n| IDENTIFY | Asset Management (ID.AM) | ID.AM-1 | Moderate Impact | ISA/IEC 62443-2- 1:2009 4.2.3.4 ISA/IEC 62443-3- 3:2013 SR 7.8 CM-8 |\n| IDENTIFY | Asset Management (ID.AM) | ID.AM-1 | Identify individuals who are both responsible and accountable for administering manufacturing system components."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy:\n\nThis publication describes the Risk Management Framework (RMF) and provides guidelines for applying the RMF to information systems and organizations. The RMF provides a disciplined, structured, and flexible process for managing security and privacy risk that includes information security categorization; control selection, implementation, and assessment; system and common control authorizations; and continuous monitoring. The RMF includes activities to prepare organizations to execute the framework at appropriate risk management levels. The RMF also promotes near real-time risk management and ongoing information system and common control authorization through the implementation of continuous monitoring processes; provides senior leaders and executives with the necessary information to make efficient, cost-effective, risk management decisions about the systems supporting their missions and business functions; and incorporates security and privacy into the system development life cycle. Executing the RMF tasks links essential risk management processes at the system level to risk management processes at the organization level. In addition, it establishes responsibility and accountability for the controls implemented within an organization's information systems and inherited by those systems."}], "metadata": {"source": "Risk Management Framework for Information Systems and Organizations_ A System Life Cycle Approach for Security and Privacy", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI:\n\nNCR C Development Toolkit\nRelease 2;\nNIST-95/1303;\n8/1 /96\n\nSCO OpenServer Development\nSystem Release 5;\nNIST-95/1941;\n\nThe FIPS PUB 128-1 requires the use of application profiles. In particular, FIPS PUB 128-1 requires\nthe use of military specification MIL-D-28003A, commonly known as the Continuous Acquisition and\nLife-Cycle Support (CALS) CGM Application Profile (AP)."}], "metadata": {"source": "Validated Products List 1995 no. 4_ Programming Languages, Database Language SQL, Graphics, POSIX, Computer Security, Product Data - IGES, OSI", "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 PDA Forensic Tools_ an Overview and Analysis:\n\nUnlike the situation with personal computers, the number and variety of toolkits for PDAs and other handheld devices is considerably limited. Not only are there fewer specialized tools and toolkits, but also the range of devices over which they operate is typically narrowed to only the most popular families of PDA devices - those based on the Pocket PC and Palm OS. Moreover, the tools require that the examiner have full access to the device (i.e. the device is not protected by some authentication mechanism or the examiner can satisfy any authentication mechanism encountered). While a couple of toolkits support a full range of acquisition, examination, and reporting functions, the remaining tools focus mainly on a single function. Table 2 lists opensource and commercially available tools and the facilities they provide for each PDA family. The abbreviation NA means that the tool at the left of the row is not applicable to the device at top of the column.\n\nPassword Protected Devices: Not Applicable - If a 4-digit pin or alphanumeric password is employed for user authentication, ActiveSync prompts for the information. Until the proper entry is made, communications/connectivity is not permitted.\n\nDevice Content Acquisition: Pocket PC 2003, officially known as Windows Mobile, requires ActiveSync 3.7 to synchronize data between a PC and the device. However, PDA Seizure version 2.5.0.0 was not able to successfully make a connection to the device with ActiveSync 3.7. In order to acquire information, ActiveSync 3.7 had to be uninstalled and replaced with ActiveSync 3.5. Thereafter, acquiring information proceeded as expected, with no connectivity problems encountered. The acquisition process for the devices, took approximately 30-60 minutes."}], "metadata": {"source": "PDA Forensic Tools_ an Overview and Analysis", "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 Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters:\n\n................................4 | Overview of Elliptic Curves ...............................................................................................4 |\n| 2.1.1.\n| Curves in Short-Weierstrass Form..............................................................................4 | |\n| 2.1.2. | Montgomery Curves....................................................................................................4 | |\n| 2.1.3. | Twisted Edwards Curves ............................................................................................5 | |\n| 2.2.1. | Curves in Short-Weierstrass Form..............................................................................5 | |\n| | Recommended Curves for U.S. Federal Government Use .............................................6 | Recommended Curves for U.S. Federal Government Use .............................................6 |\n| 3.1.1."}], "metadata": {"source": "Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters", "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 IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements:\n\ndocument should refer to NIST SP 800-161 Revision 1, Cyber Supply Chain Risk Management Practices for Systems and Organizations [800-161] to understand these responsibilities and supporting practices.\nIn addition to the specifics of the device and how it works, organizations should also consider the practices of the manufacturer in the development and on-going support of the IoT device. Secure development, supply chain, and maintenance (e.g., vulnerability management and patching) practices can help mitigate the introduction of vulnerabilities and possibly reduce likelihood and/or impact of adverse events. Consider:"}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ Establishing IoT Device Cybersecurity Requirements", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Guidelines for the Secure Deployment of IPv6:\n\nThis section provides general information about IPv6 as a foundation for later sections. The rest of this section is a resource for understanding the similarities and differences between IPv4 and IPv6, with a focus on addressing (RFC 4291). Section 3.1 discusses IPv6 addresses, how the IPv6 address space is used, and IPv6 address types and scope. This is followed by a review of IPv4 addressing and IPv4 Classless Inter-Domain Routing (CIDR) addressing. Then IPv4 and IPv6 addressing are summarized and compared. Section 3.2 covers IPv6 address allocation. IPv6 headers, their formats, and fields are discussed in Section 3.3. Sections 3.4 through 3.7 cover extension headers, ICMPv6, IPv6 routing, and IPv6 Domain Name System (DNS) respectively.\n\nIPsec coverage for multicast is incomplete. If a multicast group has more than one sender, the replay protection mechanism does not work. More importantly, IKE is a unicast UDP protocol that only works between two parties, so automated key management for multicast IPsec is lacking. For additional details about using IPsec with IPv6 multicast, see Section 5.3.3.\n\nTo enhance accountability, many organizations may prefer to use DHCPv6 and disable autoconfiguration to force authentication prior to gaining an IPv6 address. This also aids with forensics if there are verifiable logs that show which user had been leased which IPv6 address at a given time. Those logs will provide corroborating evidence in a forensic case. Another security enhancement related to DHCPv6 use is that DHCPv6 is more resilient to pool consumption attack. Because the DHCPv6 pool is typically comprised of an entire /64 subnet there are many addresses in the pool. Therefore, it is unlikely that an attacker will be able to claim all the IPv6 addresses in the pool to cause the next legitimate user's request to get rejected because all the addresses have been leased out."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to A Security Perspective on the Web3 Paradigm:\n\nOpinions and evaluations of the utility and feasibility of the Web3 vision are out of scope for this document, which takes no position on whether the Web3 vision can or should be implemented. For readers who are interested in learning about the case for Web3 adoption, a by some Web3 proponents and does not take a position on them.\n\nSince Web3 is still in the early stages of development, domain-specific best practices have not been established, and Web3 will need to build on existing best practices for software development. Web3 developers will also need to actively monitor for exploits, mitigate attacks, and quickly deploy fixes to reduce the impact of attacks. Errors and bugs can be present at any technology layer within Web3, from the blockchain itself to user interfaces, web servers, operating systems, smart contracts, data oracles, cross-chain bridges, wallet software, and even hardware. Since bugs in one layer of technology can adversely affect another layer, developers will need to monitor all layers for vulnerabilities. Testing, updating, and maintaining up-to-date information on current vulnerabilities and mitigations will help to reduce or eliminate the impact of bugs. may have many anonymous contributors with different priorities and ethics. Blockchains, cryptocurrency, and Web3 applications may not have established methods for developers to disclose bugs or errors, and end users may not know the software layer at which a specific bug"}], "metadata": {"source": "A Security Perspective on the Web3 Paradigm", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 2 require for Security Assessment?"}, {"role": "assistant", "content": "According to Assessing Security Requirements for Controlled Unclassified Information:\n\nassessment; assessment method; assessment object; assessment procedure; assurance; Controlled Unclassified Information; coverage; FISMA; NIST Special Publication 800-171; NIST Special Publication 800-53A; nonfederal organization; nonfederal system; security assessment; security requirement.\n\n- System development life cycle responsibilities (e.g., program managers, mission/business owners, information owners/stewards, system designers and developers, system/security engineers, systems integrators)\n- Acquisition or procurement responsibilities (e.g., contracting officers)\n- System, security, or risk management and oversight responsibilities (e.g., authorizing officials, chief information officers, chief information security officers, system owners, information security managers)\n- Security assessment and monitoring responsibilities (e.g., auditors, system evaluators, assessors, independent verifiers/validators, analysts)\n\n- Federal perspective : The entity establishing and conveying security assessment requirements in contractual vehicles or other types of agreements\n- Nonfederal perspective : The entity responding to and complying with the security assessment requirements set forth in contracts or agreements"}], "metadata": {"source": "Assessing Security Requirements for Controlled Unclassified Information", "cmmc_level": "2", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Analyzing Collusion Threats in the Semiconductor Supply Chain:\n\n## Analyzing Collusion Threats in the Semiconductor Supply Chain\n\nRekhi S, Amberiadis K, Akib AA, Srivastava A (2025) Analyzing Collusion Threats in the Semiconductor Supply Chain. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Cybersecurity White Paper (CSWP) NIST CSWP 46. https://doi.org/10.6028/NIST.CSWP.46\n\nThis work proposes a framework for analyzing threats related to the semiconductor supply chain. The framework introduces a metric that quantifies the severity of different threats subjected to a collusion of adversaries from different stages of the supply chain. Two different case studies are provided to describe the real-life application of the framework. The metrics and analysis aim to guide security efforts and optimize the trade-offs of hardware security and costs."}], "metadata": {"source": "Analyzing Collusion Threats in the Semiconductor Supply Chain", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Computer Security Division 2006 Annual Report:\n\ns' Association (FISSEA), the Federal Computer Security Program Managers' Forum (FCSM Forum), the Small Business Corner, and the Program Review for Information Security Management Assistance (PRISMA).\n- Evaluate security policies and technologies from the private sector and national security systems for potential Federal agency use - Host a growing repository of Federal agency security practices, public/private security practices, and security configuration checklists for IT products. In conjunction with the Government of Canada's Communications Security Establishment, CSD leads the Cryptographic Module Validation Program (CMVP). The Common Criteria Evaluation and Validation Scheme (CCEVS) and CMVP facilitate security testing of IT products usable by the Federal government. - Solicit recommendations of the Information Security and Privacy Advisory Board on draft standards and guidelines -Solicit recommendations of the Board regularly at quarterly meetings. - Provide outreach, workshops, and briefings - Conduct ongoing awareness briefings and outreach to our customer community and beyond to ensure comprehension of guidance and awareness of planned and future activities. We also hold workshops to identify areas our customer community wishes addressed, and to scope guidance in a collaborative and open format. - Satisfy annual NIST reporting requirement - Produce an annual report as a NIST Interagency Report (IR). The 2003, 2004, and 2005 Annual Reports are available via the Web or upon request."}], "metadata": {"source": "Computer Security Division 2006 Annual Report", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements:\n\nThe SCAP specification describes the SCAP components at a high level and how the components relate to each other within the context of SCAP. The SCAP specification does not define the SCAP components in detail; each component has its own standalone specification document or reference. The SCAP components were created and are maintained by several entities, including NIST, the MITRE Corporation, the National Security Agency (NSA), and the Forum of Incident Response and Security Teams (FIRST).\n\nForum of Incident Response and Security Teams"}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements", "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 Guidelines for Evaluating Differential Privacy Guarantees:\n\nerential Privacy With Other Data Releases . . . | Mixing Differential Privacy With Other Data Releases . . . | 27 |\n| 2.7. | Auditing and Empirical Measures of Privacy | . . . .\n. . | 28 |\n| 3. Differentially Private Algorithms . . . . . . . . | 3. Differentially Private Algorithms . . . . . . . . | . . . . . . . . | 29 |\n| 3.1. | Basic Mechanisms and Common Elements . | . . . . . . | 29 |\n| 3.2. | Utility and Accuracy . . . | . . . . . . . . . . . . . . . . . | 31 |\n| 3.3. | Bias . . . . . . . . . . . . . . . . . . | . . . . . . . . . . . | 35 |\n| | 3.3.1. | Systemic Bias . . . . . . . . . . . . . . . . . . . | 36 |\n| | 3.3.2. | Human Bias . . . . . . . . . . . . . . . . . . . . | 37 |\n| | 3.3.3. | Statistical Bias . . . . . . . . . . . . . . . . . . | 38 |\n| 3.4. | Analytics Queries . | . . . . . . . . . . . . . . . . . . . . . | 40 |\n| | 3.4.1. | Counting Queries . . . . . . . . . . . . . . . . . | 40 |\n| | 3.4.2. | Summation Queries . . . . . . . . . . . . . . . . | 43 |\n| | 3.4.3. | Average Queries . . . . . . . . . . . . . . . . . . | 44 |\n| | 3.4.4. | Min/Max Queries . . . . . . . . . . . . . . . . . | 44 |\n| 3.5. | Machine Learning | . . . . . . . . . . . . . . . . . . . . . | 44 |"}], "metadata": {"source": "Guidelines for Evaluating Differential Privacy Guarantees", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cybersecurity of Genomic Data provide? (Part 3)"}, {"role": "assistant", "content": "to the individual, industry, and government because it has multiple intrinsic properties that in combination make it different from other types of data that possess only a subset of these properties.\nThe characteristics of genomic data compared to other datasets raise some correspondingly unique cybersecurity and privacy concerns that are inadequately addressed with current policies, guidance documents, and technical controls. This report describes current practices in cybersecurity and privacy risk management for protecting genomic data, along with relevant challenges and concerns identified during 2022 NCCoE-hosted workshops with bioeconomy stakeholders and subsequent related research. Gaps that were identified by stakeholders include: practices across the lifecycle concerning genomic data generation; safe and responsible sharing of genomic data; monitoring the systems processing genomic data; lack of specific guidance documents addressing the unique needs of genomic data processors; and regulatory/policy gaps with respect to national security and privacy threats in the collection, storage, sharing, and aggregation of human genomic data. The report proposes a set of solution ideas that address real-life use cases occurring at various stages of the genomic data lifecycle along with candidate mitigation strategies and the expected benefits of the solutions. The solutions recorded in this report reflect the bioeconomy workshop stakeholders' proposed actions and activities. ## Keywords\n\nCyberbiosecurity; cybersecurity; genomic data; genomics; human genome; privacy. ## 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": "Cybersecurity of Genomic Data", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Security Guidelines for Storage Infrastructure:\n\n'…the extent to which an entity is threatened by a potential circumstance or event. Risk typically is a function of: (i) the adverse impacts that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence. Information system-related security risks arise from the loss of confidentiality, integrity, or availability of information or information systems. These risks reflect the potential adverse impacts to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, other organizations, and the Nation.' [28]\n\n- (a) Cover all data assets of the enterprise irrespective of where they reside (i.e., on-premises or in the cloud). It is acceptable to refrain from protecting data assets with no significance to the organization, or that can be re-created from other protected data sources within the required RTO, but such omissions should be documented. - (b) Be organized by the type of data involved (e.g., Tier 1, Tier 2, etc.). - (c) Consider data integrity at the application and business process levels (e.g., if two components should be recovered to the same point in time to function properly, then federated consistency mechanisms or equivalent should be planned and implemented). - (d) Consider the required restoration speed to meet business or regulatory requirements - so that implementation would be based on technology stacks with appropriate characteristics (e.g., disk-based, point-in-time copies such as snapshots or clones, vs. tape or over-WAN recovery). - (a) Monitor the execution of backups based on policy and associated notification mechanisms. - (b) Periodically test backups (at least monthly for critical data) to verify their integrity and their ability to be restored."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities:\n\nOrganizations have information technology (IT) plans in place, such as contingency and computer security incident response plans, so that they can respond to and manage adverse situations involving IT. These plans should be maintained in a state of readiness, which should include having personnel trained to fulfill their roles and responsibilities within a plan, having plans exercised to validate their content, and having systems and system components tested to ensure their operability in an operational environment specified in a plan. These three types of events can be carried out efficiently and effectively through the development and implementation of a test, training, and exercise (TT&E) program. Organizations should consider having such a program in place because tests, training, and exercises are so closely related. For example, exercises and tests offer different ways of identifying deficiencies in IT plans, procedures, and training. This document provides guidance on designing, developing, conducting, and evaluating TT&E events so that organizations can improve their ability to prepare for, respond to, manage, and recover from adverse events that may affect their missions. The scope of this document is limited to TT&E events for single organizations, as opposed to large-scale events involving multiple organizations, involving internal IT operational procedures for emergencies. This document does not address TT&E for a specific type of IT plan; rather, the TT&E methodology described in this document can be applied to TT&E events built around any IT plan or around an IT emergency-handling capability that is not necessarily documented in a plan, such as computer security incident response. Organizations should conduct TT&E events periodically; following organizational changes, updates to an IT plan, or the issuance of new TT&E guidance; or as otherwise needed."}], "metadata": {"source": "Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to The Keyed-Hash Message Authentication Code (HMAC):\n\n5. Maintenance Agency. Department of Commerce, National Institute of Standards and Technology, Information Technology Laboratory (ITL).\n6. Applicability. This Standard is applicable to all Federal departments and agencies for the protection of sensitive unclassified information that is not subject to Title 10 United States Code Section 2315 (10 USC 2315) and that is not within a national security system as defined in Title 44 United States Code Section 3502(2) (44 USC 3502(2)). The adoption and use of this Standard is available to private and commercial organizations.\n7. Specifications. Federal Information Processing Standard (FIPS) 198-1, The KeyedHash Message Authentication Code (HMAC) (affixed).\n8. Implementations. The authentication mechanism described in this Standard may be implemented in software, firmware, hardware, or any combination thereof. NIST has developed a Cryptographic Module Validation Program that will test implementations for conformance with this HMAC Standard. Information on this program is available at http://csrc.nist.gov/groups/STM/index.html."}], "metadata": {"source": "The Keyed-Hash Message Authentication Code (HMAC)", "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 Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC:\n\nThe Counter mode decryption function has a vulnerability that is arguably more serious. Counter-mode ciphertext is 'malleable' in the sense that flipping any of its bits will induce the corresponding bits of the plaintext to flip upon decryption. Therefore, if an adversary knows a plaintext-ciphertext pair and can induce the decryption function to use the counter blocks from the known pair, then, by choosing which bits to flip in the known ciphertext, the adversary can control the result of decryption, up to the length of the known plaintext.\n\nThis vulnerability motivates combining the Counter mode encryption mechanism with an authentication mechanism, such as occurs in GCM. The idea is to prevent the adversary's altered ciphertext from being accepted as valid. However, as detailed in Ref. [5], the authentication assurance in GCM crucially depends on the uniqueness of the IVs."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC", "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 IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog provide? (Part 2)"}, {"role": "assistant", "content": "approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130.\nNothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-213A Natl. Inst. Stand. Technol. Spec. Publ. 800-213A, 94 pages (November 2021) CODEN: NSPUE2\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-213A\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": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\nFigure 8 displays entities as having distinct roles, but some may have multiple roles, such as an organization and providing retail products to also the measures it may take to manage data processing ecosystem encompasses may have multiple component suppliers. providing services to other organizations\n\nIn circumstances where it may not be possible to impose a set of privacy requirements on the supplier, the objective should be to make the best buying decision among multiple suppliers, given a carefully determined list of privacy requirements. Often, this means some degree of trade-off, comparing multiple products or services with known gaps to the Profile. If the system, product, or service purchased did not meet all of the objectives described in the Profile, an organization could address the residual risk through mitigation measures or other management actions. - Privacy Risk Management Process -Organizational privacy risk management practices are not formalized, and risk is managed in an ad hoc and sometimes reactive manner. Prioritization of privacy activities may not be directly informed by organizational risk management priorities, privacy risk assessments, or mission or business objectives. - Integrated Privacy Risk Management Program -There is limited awareness of privacy risk at the organizational level. The organization implements privacy risk management on an irregular, case-by-case basis due to varied experience or information gained from outside sources. The organization may not have processes that enable the sharing of information about data processing and resulting privacy risks within the organization. - Data Processing Ecosystem Relationships - There is limited understanding of an organization's role(s) in the larger ecosystem with respect to other entities (e.g., buyers, suppliers, service providers, business associates, partners)."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "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 Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure:\n\n| | Introduction .........................................................................................................................1 | Introduction .........................................................................................................................1 | |---------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| | | Purpose.........................................................................................................................2 | | | | Scope............................................................................................................................2 | | | | Audience | .......................................................................................................................4 | | Intended Use........................................................................................................................5 | Intended Use........................................................................................................................5 | | | | EV/XFC Cybersecurity Mission Objectives.......................................................................5 | EV/XFC Cybersecurity Mission Objectives.......................................................................5 | | | Mission Objective 1: Deliver Reliable Performance through Secure Communications.6 | | | | Mission Objective 2: Maintain Resilience of the XFC Infrastructure..............................7 | | | | Mission Objective 3: Build and Maintain Trustworthy Relationships with Partners and Customers..............................................................................................................7 | | | | Mission Objective 4: Maintain Continuity of Operations................................................8 | | | | Overview of the Cybersecurity Framework ......................................................................8 | | | | The Framework Core ....................................................................................................9 | | | | Sector-Level Profiles | ...................................................................................................12 | | | XFC Baseline Profile .........................................................................................................12 | | | | Identify Function..........................................................................................................12 | | | 5.1.1."}], "metadata": {"source": "Cybersecurity Framework Profile for Electric Vehicle Extreme Fast Charging Infrastructure", "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 Application Container Security Guide:\n\nCM-6, CP-2, CP-4, IR-2, IR-3, IR-8, PE-6, SC-5, SC-7, SI-3, SI-4, SI-7 | EO 13587; NIST SP 800-61 | | MA-2, Controlled Maintenance | CM-3, CM-4, MA-4, MP-6, PE-16, SA-12, SI-2 | | | MA-4, Nonlocal Maintenance | AC- 2, AC-3, AC-6, AC-17, AU-2, AU-3, IA-2, IA-4, IA-5, IA-8, MA-2, MA-5, MP-6, PL-2, SC-7, SC-10, SC-17 | FIPS 140-2, 197, 201; NIST SPs 800-63, 800-88; CNSS Policy 15 | | PL-2, System Security Plan | AC-2, AC-6, AC-14, AC-17, AC-20, CA-2, CA-3, CA-7, CM-9, CP-2, IR-8, MA-4, MA-5, MP-2, MP-4, MP-5, PL-7, PM-1, PM-7, PM-8, PM-9, PM-11, SA-5, SA-17 | NIST SP 800-18 | | PL-4, Rules of Behavior | AC-2, AC-6, AC-8, AC-9, AC-17, AC-18, AC-19, AC-20, AT-2, AT-3, CM-11, IA-2, IA-4, IA-5, MP-7, PS-6, PS-8, SA-5 | NIST SP 800-18 | | RA-2, Security Categorization | CM-8, MP-4, RA-3, SC-7 | FIPS 199; NIST SPs 800-30, 800-39, 800-60 | | RA-3, Risk Assessment | RA-2, PM-9 | OMB Memorandum 04-04; NIST SPs 800-30, 800-39; https://idmanagement.gov/ | | SA-10, Developer Configuration Management | CM-3, CM-4, CM-9, SA-12, SI-2 | NIST SP 800-128 | | SA-11, Developer Security Testing and Evaluation | CA-2, CM-4, SA-3, SA-4, SA-5, SI-2 | ISO/IEC"}], "metadata": {"source": "Application Container Security Guide", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Recommendation for Stateful Hash-Based Signature Schemes:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. This publication supplements FIPS 186 [4] by specifying two additional digital signature schemes, both of which are stateful hash-based signature (HBS) schemes: the Leighton-Micali Signature (LMS) system [2] and the eXtended Merkle Signature Scheme (XMSS) [1], along with their multi-tree variants, the Hierarchical Signature System (HSS) and multi-tree XMSS (XMSS MT )."}], "metadata": {"source": "Recommendation for Stateful Hash-Based Signature Schemes", "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 Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio:\n\n| Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| | Introduction ...................................................................................................................... | 5 |\n| 1.1 | Purpose and Scope.................................................................................................... | 5 |\n| 1.2 | Document Structure...................................................................................................."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "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 Building Secure Microservices-based Applications Using Service-Mesh Architecture 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 100 Bureau Drive (Mail Stop 8930) Gaithersburg, MD 20899-8930\n\nAttn: Computer Security Division, Information Technology Laboratory Email: sp800-204a-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\nThe increasing trend in building microservices-based applications calls for addressing security in all aspects of service-to-service interactions due to their unique characteristics. The distributed cross-domain nature of microservices needs secure token service (STS), key management and encryption services for authentication and authorization, and secure communication protocols."}], "metadata": {"source": "Building Secure Microservices-based Applications Using Service-Mesh Architecture", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guide to Information Technology Security Services:\n\nPlanning ..................................................................................5-6 | | | 5.2.2 | Incident Handling..........................................................................................5-7 | | | 5.2.3 | Testing..........................................................................................................5-8 | | | 5.2.4 | Training ........................................................................................................5-9 | | 5.3 | Technical Security Services...................................................................................5-11 | Technical Security Services...................................................................................5-11 | | | 5.3.1 | Firewalls .....................................................................................................5-11 | | | 5.3.2 | Intrusion Detection .....................................................................................5-11 | | | 5.3.3 | Public Key Infrastructure ............................................................................5-12 | | Appendix A-REFERENCES.................................................................................................A-1 | Appendix A-REFERENCES.................................................................................................A-1 | Appendix A-REFERENCES.................................................................................................A-1 | | Appendix B-ACRONYM LIST..............................................................................................B-1 | Appendix B-ACRONYM LIST..............................................................................................B-1 | Appendix B-ACRONYM LIST..............................................................................................B-1 | | Appendix C-SERVICE AGREEMENT OUTLINE................................................................"}], "metadata": {"source": "Guide to Information Technology Security Services", "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 Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment:\n\not the results of the ISCM program or the continuous monitoring technologies used . An effective ISCM program assessment provides consistent results regardless of the entity conducting the assessment.\nThis publication does not prescribe the assessment of individual controls nor the examination of control assessment results as part of the ISCM program assessment."}], "metadata": {"source": "Assessing Information Security Continuous Monitoring (ISCM) Programs_ Developing an ISCM Program Assessment", "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 Key Performance Indicators for Process Control System Cybersecurity Performance Analysis:\n\nThe Process Control System emulates an industrial continuous manufacturing system, a manufacturing process to produce or process materials continuously, where the materials are moving, going through chemical reactions, or undergoing mechanical or thermal treatment continuously. Continuous manufacturing usually implies a 24x7 operation with infrequent maintenance shutdowns and is contrasted with batch manufacturing. Examples of continuous manufacturing systems include chemical production, oil refining, natural gas processing, and waste water treatment.\n\nOnce in the run mode, the Plant Simulator will start sending and receiving sensor and actuator values to and from the PLC. The OPC server polls the PLC at a data rate of 10Hz to exchange sensor and actuator values. The OPC server will send updated sensor values to the subscribing clients, namely, the Controller, HMI, and Data Historian. The OPC server operates in exceptionreport mode, meaning it will only send updates to clients when the data changes. When the\n\nA control counter is added to the DeviceNet interface and the PLC. This control counter increments every simulation cycle of the Plant Simulator and in turn updates the PLC through the DeviceNet. By measuring the round trip time of the counter, it serves as a control value for network latency between the Plant Simulator and the Controller."}], "metadata": {"source": "Key Performance Indicators for Process Control System Cybersecurity Performance Analysis", "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 Securing Wireless Local Area Networks (WLANs) provide? (Part 3)"}, {"role": "assistant", "content": "ves from the Department of Justice and the Office of the Director of National Intelligence. ## Trademark Information\n\nAll trademarks and registered trademarks belong to their respective organizations.\n## Table of Contents\n\n| Executive Summary.................................................................................................................vi | Executive Summary.................................................................................................................vi | Executive Summary.................................................................................................................vi |\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. | Introduction ...................................................................................................................... 1 | Introduction ......................................................................................................................"}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Best Practices for Privileged User PIV Authentication:\n\ne IA-2 control enhancements (1), (3), (6), (8), (11), and (12). |\n| IA-4, Identifier Management | Manage information system identifiers for all privileged users.\n|\n| IA-5, Authenticator Management | Manage information system authenticators for all privileged users. IA-5 control enhancements of particular interest include (1), (2), and (11). |\n| IA-8, Identification and Authentication (Non-Organizational Users) | Uniquely identify and authenticate each privileged user. Also, see IA-8 control enhancements (1) and (5). |\n| SC-8, Transmission Confidentiality and Integrity | Protect the confidentiality and integrity of all communications related to privileged user authentication and privileged sessions. |\n| SC-10, Network Disconnect | Terminate network connections from privileged accounts after a defined period of inactivity. |\n| SI-2, Flaw Remediation | Apply patches and other updates to correct vulnerabilities in protocols, services, etc. used for privileged user authentication. |\n| SI-4, Information System Monitoring | Perform ongoing monitoring of all privileged account usage. SI-4 control enhancements of particular interest include (20). |"}], "metadata": {"source": "Best Practices for Privileged User PIV Authentication", "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 Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\nooks like for that system, which in turn allows the organization to identify deviations from that 'normal.' This is a foundational piece of the information security measurement and assessment process.\n|\n| Control Assessment | Exploratory Data Analysis | At the control level, a multi-factor/comparative box plot could be used to compare the key characteristics or unusual data in a data set monitoring a control. |\n| Control Assessment | Bayesian/predictive | The Bayesian/predictive method may be used to make decisions about the frequency of equipment maintenance using SP 800-53 control MA-6(2), Timely Maintenance | Predictive Maintenance, and historical data about organizational equipment. |"}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Computer Security Division 2015 Annual Report:\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": "Computer Security Division 2015 Annual Report", "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 Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0 provide? (Part 3)"}, {"role": "assistant", "content": "nd the private sector, uses a common language to address and manage cybersecurity risk in a cost-effective way based on business needs without placing additional regulatory requirements on businesses.\nThe Framework focuses on using business drivers to guide cybersecurity activities and considering cybersecurity risks as part of the organization's risk management processes. The Framework consists of three parts: the Framework Core, the Framework Profile, and the Framework Implementation Tiers. The Framework Core is a set of cybersecurity activities, outcomes, and informative references that are common across critical infrastructure sectors, providing the detailed guidance for developing individual organizational Profiles. Through use of the Profiles, the Framework will help the organization align its cybersecurity activities with its business requirements, risk tolerances, and resources. The Tiers provide a mechanism for organizations to view and understand the characteristics of their approach to managing cybersecurity risk. The Executive Order also requires that the Framework include a methodology to protect individual privacy and civil liberties when critical infrastructure organizations conduct cybersecurity activities. While processes and existing needs will differ, the Framework can assist organizations in incorporating privacy and civil liberties as part of a comprehensive cybersecurity program. The Framework enables organizations - regardless of size, degree of cybersecurity risk, or cybersecurity sophistication - to apply the principles and best practices of risk management to improving the security and resilience of critical infrastructure. The Framework provides organization and structure to today's multiple approaches to cybersecurity by assembling standards, guidelines, and practices that are working effectively in industry today."}], "metadata": {"source": "Framework for Improving Critical Infrastructure Cybersecurity, Version 1.0", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\nIdeally, the CSF will be used to address cybersecurity risks alongside other risks of the enterprise, including those that are financial, privacy, supply chain, reputational, technological, or physical in nature. - improvement opportunities for the organization's policies, plans, processes, procedures, and practices that support cybersecurity risk management to inform efforts under all six Functions. - PROTECT (PR) -Safeguards to manage the organization's cybersecurity risks are used. Once assets and risks are identified and prioritized, PROTECT supports the ability to secure those assets to prevent or lower the likelihood and impact of adverse cybersecurity events, as well as to increase the likelihood and impact of taking advantage of opportunities. Outcomes covered by this Function include identity management, authentication, and access control; awareness and training; data security; platform security (i.e., securing the hardware, software, and services of physical and virtual platforms); and the resilience of technology infrastructure. - DETECT (DE) -Possible cybersecurity attacks and compromises are found and analyzed. DETECT enables the timely discovery and analysis of anomalies, indicators of compromise, and other potentially adverse events that may indicate that cybersecurity attacks and incidents are occurring. This Function supports successful incident response and recovery activities. - RESPOND (RS) -Actions regarding a detected cybersecurity incident are taken. RESPOND supports the ability to contain the effects of cybersecurity incidents. Outcomes within this Function cover incident management, analysis, mitigation, reporting, and communication. - RECOVER (RC) -Assets and operations affected by a cybersecurity incident are restored. RECOVER supports the timely restoration of normal operations to reduce the effects of cybersecurity incidents and enable appropriate communication during recovery efforts."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium:\n\n-  Current research in Cyber Physical Systems is focused on Supervisory Control and Data Acquisition (SCADA) systems, but Additive Manufacturing is different. -  Researchers were able to intercept a job initialization file and decode it, allowing attackers to potentially alter printer parameters mid-print. The STL (or newer AMF) standard files are especially vulnerable to attacks which alter a design. -  The presenters described an experiment run on students at Virginia Tech. Seven groups of students were given an 'extra credit' assignment to design a standard dog bone, print it, and test it. An exploit was easily developed which inserted a void in the STL file. Students failed to recognize any anomalies prior to printing and testing. No students correctly diagnosed the anomalies as a cybersecurity problem. -  Recommendations include improved quality control processes, hashing, improved process monitoring, and operator training. -  Some attendees commented that other forms of manufacturing have similar vulnerabilities. -  Cybersecurity solutions should be built under the assumption that manufacturers are not cybersecurity experts. 2500 Plus machine) using Nylon 12 powder. Upon testing, all of the specimens containing voids fractured at the void location, while the specimens without voids failed normally. The average reduction in yield load was 14%, from 1085N to 930N, and the strain at failure was reduced from 10.4% to 5.8%. Abstract - Applying meaningful and assessing impactful cybersecurity controls are ongoing and significant challenges for the Direct Digital Manufacturing (DDM) Community. These issues will be significant as the technology moves into the mainstream manufacturing supply chain. This presentation will, therefore, address cybersecurity threats to DDM, including insight into potential attack scenarios and motivations, gained through direct observations."}], "metadata": {"source": "Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to 1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report):\n\n| BURROWS | AND | | PATRICK R. | GALLAGHER, | JR. | . | . V | | | | | | | | | | |\n| LETTER | FROM | EUGENE F. | TROY | AND | CHRISTOPHER | | P. BYTHEWOOD, | | JR."}], "metadata": {"source": "1989 Computer Security and Privacy Plans (CSPP) Review Project_ A First-Year Federal Response to the Computer Security Act of 1987 (Final Report)", "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 Security of SQL-Based Implementations of Product Data Exchange Using STEP:\n\n3.1.2 Inference and Aggregation\n\nInference and aggregation are not addressed in the SQL specifications, but can be addressed through add-on tools. 3.1.2)."}], "metadata": {"source": "Security of SQL-Based Implementations of Product Data Exchange Using STEP", "cmmc_level": "all", "nist_control": "3.1.2", "cmmc_practice_id": "AC.L2-3.1.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic:\n\nevelopment practices. Moreover, complex medical devices invoke specialized requirements, such as detailed design diagrams, evidence of rigorous vulnerability assessments, and supporting documentation.\nAt the conclusion of the assessment, the OIS provides a cybersecurity risk report to SCM who assists the business proponent in making a procurement decision based on this report and on the supplier's bankability and regulatory status. Suppliers must conduct external information security assessments and penetration tests annually, and the Mayo Clinic reserves the right to verify conformance with site audits at the suppliers' facilities. The Mayo Clinic declines to work with suppliers that present high instability or cybersecurity supply chain risk if they cannot effectively mitigate those risks."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Mayo Clinic", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Privacy Protection in the United States_ A 1991 Survey of Laws and Regulations Affecting Privacy in the Public and Private Sector Including a List of :\n\nRestricts Federal agencies from disclosing personal data except for publicly announced purposes, and requires agencies (1) to keep an accounting of extra-agency disclosures, (2) to instruct record management personnel in the requirements of the Act and the rules for its implementation, and (3) to \"establish appropriate administrative, technical, and physical safeguards to insure the security and confidentiality of records . ''\n\nEmployment Records Statutes -Prohibit employers from collecting information about a job applicant's race, sex, color, religion, national origin, and other attributes. Allow individuals access to personnel records held by their employers. See . Cal. Lab. Code § 1198.5; Colo. Rev. Stat. § 24-24-301; Conn. Gen. Stat. § 31-128a; Del. Code tit. 19, § 723; Hawaii Rev. Stat. § 378-1; 111. Stat. ch. 48, § 2001; Me. Rev. Stat. tit. 26, § 631; Mass. Gen. Laws ch, 149, § 52C; Mich. Comp. Laws § 423.501; Nev . Rev. Stat. § 613.075; N.H. Rev. Stat. § 275.56; Ohio Rev. Code § 4113.23; Or. Rev. Stat. § 652.750; Pa. Stat. tit. 43, § 1321; R.I. Gen. Laws § 28-6.4-1; S.D. Codified Laws § 3-6A-31; Wash. Rev. Code 49 . 12.250.\n\nThe Privacy Act also generally prohibits Federal agencies from disclosing personal data except for publicly announced purposes, and requires agencies (1) to keep an accounting of extra-agency disclosures, (2) to instruct record management personnel in the requirements of the Act and the rules for its implementation, and (3) to \"establish appropriate administrative, technical, and physical safeguards to insure the security and confidentiality of records.\" 5 U.S.C. 552a."}], "metadata": {"source": "Privacy Protection in the United States_ A 1991 Survey of Laws and Regulations Affecting Privacy in the Public and Private Sector Including a List of ", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Cloud Computing Synopsis and Recommendations:\n\n| | 6.4.1 | Lack of Portability between PaaS Clouds................................................... | 6-4 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| | 6.4.2 | Event-based Processor Scheduling ........................................................... | 6-4 |\n| | 6.4.3 | Security Engineering of PaaS Applications ................................................"}], "metadata": {"source": "Cloud Computing Synopsis and Recommendations", "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 Strategies for Microservices-based Application Systems:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST. The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in Federal information systems. The 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. Microservices architecture is increasingly being used to develop application systems since its smaller codebase facilitates faster code development, testing, and deployment as well as optimization of the platform based on the type of microservice, support for independent development teams, and the ability to scale each component independently."}], "metadata": {"source": "Security Strategies for Microservices-based Application Systems", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to General Access Control Guidance for Cloud Systems:\n\nA cloud system that deploys the SaaS model can be accessible over a network by an end user utilizing various client devices (e.g., a thin client interface, such as a web browser, for accessing a web-based email application) or via a program with the correct set of interfaces whose execution would enable communication with a cloud application. In the SaaS model, an application user is limited to user-specific application configuration settings and does not manage or control the underlying cloud infrastructure, which typically includes the network, servers, operating systems, storage, or individual applications. The PaaS model in a cloud system allows developers to create and deploy applications onto the cloud infrastructure using programming languages, libraries, services, and tools. A software developer does not manage or control the underlying cloud infrastructure but has control over the deployed applications (software) and, possibly, configuration settings for the application-hosting environment. SaaS applications provide application-specific access control configurations for different user applications, and in this case, user policies for each application are enforced by the SaaS provider. This configuration does not support collaboration between the SaaS provider and the consumer's access control infrastructure. For example, while large organizations often employ on-premises access control systems for managing their users centrally and efficiently, SaaS applications typically provide organizations with an AC configuration interface for managing AC policies, which forces the AC policies to be stored and evaluated on the SaaS provider's side. This approach might result in disclosing sensitive data required for evaluating the AC policies to the SaaS provider."}], "metadata": {"source": "General Access Control Guidance for Cloud Systems", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Security Considerations for Remote Electronic UOCAVA Voting:\n\nElection officials that administer elections use the election management console. The election management console provides an interface to the voting system so administrative task, such as the configuration of ballots, defining the time and date to cast ballots, setting up the tallying rules for the election contests, and the generation of election reports, can be completed. The election management console can be located in the same place as the voting system or may be at some other location (such as the office of the election officials).\n\ninstall and configure applications or have unrestricted access to the remote electronic voting system equipment. Election officials will have access to election data, such as cast ballots and system event logs, on the remote electronic voting system that most other authorized users may not. Access to the election data may allow a malicious election official to modify the results of the election, monitor how people vote, and provide incorrect ballot configurations.\n\nSimilar to the voter and voters' platform, the election official and election management console may pose a threat to the voting system without the election official's knowledge. If the election management console contains malware, the console may try to prevent ballots from being cast, alter ballot configurations, monitor how voters vote, and use the election official's credential to gain and expand access to damage the voting system, change election results, and harm the credibility of the election results. Although the election official is not actively participating in attacking the remote electronic voting system, the console they use to interact with the voting system poses a threat that appears to be from an election official."}], "metadata": {"source": "Security Considerations for Remote Electronic UOCAVA Voting", "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 Guide for Security-Focused Configuration Management of Information Systems:\n\n- Individuals with system and information security management and oversight responsibilities (e.g., chief information officers, senior agency information security officers, and authorizing officials);\n- Individuals with system development responsibilities (e.g., program and project managers, mission/application owners, system designers, system and application programmers);\n- Individuals with security implementation and operational responsibilities (e.g., system owners, information owners and stewards, system administrators, system security officers); and\n- Individuals with system and information security assessment and monitoring responsibilities (e.g., auditors, Inspectors General, assessors/assessment teams).\n\n- -Configuration Monitoring - process for assessing or testing the level of compliance with the established baseline configuration and mechanisms for reporting on the configuration status of items placed under CM.\n\nConfiguration change control is the documented process for managing and controlling changes to the configuration of a system or its constituent CIs. Configuration change control for the system involves the systematic proposal, justification, implementation, test/evaluation, review, and disposition of changes to the system, including upgrades and modifications. Configuration change control is applied to include changes to components of the system, changes to the configuration settings for information technology products, emergency/unscheduled changes, and changes to remediate flaws. Changes are controlled from the time the change is proposed to the implementation and testing of the change. Each step in the change process is clearly articulated along with the responsibilities and authorities of the roles involved."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of Information Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Glossary of Computer Security Terminology:\n\nhandshaking procedures | 1) A dialogue between a user and a computer, a computer and another computer, a program and another program for the purpose of Identifying a user and authenticating identity.\nA sequence of questions and answers is used based on information either previously stored in the computer or supplied to the computer by the Initiator of the dialogue. (AR 380-380; FIPS PUB 39) |\n| | 2) Synonymous with PASSWORD DIALOGUE. |\n| hardware security | Computer equipment features or devices used in an ADP system to preclude unauthorized data access. (AR 380-380) |\n| hash total | The use of specific mathematical formulae to produce a quantity that is (often appended to and) used as a check-sum or validation parameter for the data that it protects. (WB) |\n| hidden sections | Menu options, or entire sub-menus, not visible or accessible to a user due to lack of adequate authorization. (BBD) |"}], "metadata": {"source": "Glossary of Computer Security Terminology", "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 Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out:\n\nSecurity is not a one-time activity. It Is an integral part of the installation/system lifecycle. The activities described by the SOWs in this document generally require either periodic upddting or appropriate revision. These changes are made when configurations and other conditions and circumstances change significantly, or as required by federal regulations.\n\n- o review of the operating system and its installation;\n- o backup and restore procedures;\n- o review of system exits;\n- o verification of audit trails;\n- o review of handling and availability of system logs;\n- o identification of change control procedures (installation of new software releases);\n- o check for procedures which ensure that software patches are kept current;\n- o review of installation for integrity;\n- o review interfaces to access control package (if installed);\n- o identification of primary access control software and files and procedures for ensuring that all software runs under its control;\n- o review of access authorizations for appropriateness and completeness; and\n- o review of interfaces with the access control package for integrity.\n\n- o methods for developing and documenting application controls;\n- o adherence to SDLC:\n- a review of quality assurance and testing procedures;\n- change control procedures for corrections and enhancements;\n- o check for procedures which ensure that software patches are kept current;\n- o system documentation and security standards and adherence to both; and\n- o application operation and access to applications."}], "metadata": {"source": "Sample Statement of Work for Federal Computer Security Services_ For use In-House or Contracting Out", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program:\n\nner RK (2020) Integrating Cybersecurity and Enterprise Risk Management (ERM). (National Institute of Standards and Technology, Gaithersburg, MD), NIST Interagency or Internal Report (IR) NIST IR 8286.\nhttps://doi.org/10.6028/NIST.IR.8286\n- [7] National Institute of Standards and Technology (2006) Minimum Security Requirements for Federal Information and Information Systems. (U.S. Department of Commerce, Washington, DC), Federal Information Processing Standards Publication (FIPS) 200. https://doi.org/10.6028/NIST.FIPS.200\n- [8] Software Quality Group (2021) Metrics and Measures. (National Institute of Standards and Technology, Gaithersburg, MD). Available at https://www.nist.gov/itl/ssd/softwarequality-group/metrics-and-measures\n- [9] Chew E, Swanson MA, Stine KM, Bartol N, Brown A, Robinson W (2008) Performance Measurement Guide for Information Security. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-55, Rev. 1. https://doi.org/10.6028/NIST.SP.800-55r1\n- [10] Schroeder K, Trinh H, Pillitteri VY (2024) Measurement Guide for Information Security: Volume 1 - Identifying and Selecting Measures. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-55v1. https://doi.org/10.6028/NIST.SP.800-55v1"}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 2 — Developing an Information Security Measurement Program", "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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC:\n\n| Table of Contents | Table of Contents | Table of Contents | Table of Contents | |-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | PURPOSE...........................................................................................................................................................1 | PURPOSE...........................................................................................................................................................1 | PURPOSE...........................................................................................................................................................1 | | 2 | AUTHORITY.....................................................................................................................................................1 | AUTHORITY.....................................................................................................................................................1 | AUTHORITY.....................................................................................................................................................1 | | 3 | INTRODUCTION..............................................................................................................................................1 | INTRODUCTION..............................................................................................................................................1 | INTRODUCTION..............................................................................................................................................1 | | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | 4 DEFINITIONS, ABBREVIATIONS, AND SYMBOLS.................................................................................2 | | 4.1 | 4.1 | DEFINITIONS AND ABBREVIATIONS .............................................................................................................2 | | | 4.2 | 4.2 | SYMBOLS ....................................................................................................................................................5 | | | 4.2.1 | 4.2.1 | Variables................................................................................................................................................5 | | | 4.2.2 | 4.2.2 | Operations and Functions .....................................................................................................................6 | | | 5 ELEMENTS OF GCM......................................................................................................................................7 | 5 ELEMENTS OF GCM......................................................................................................................................7 | 5 ELEMENTS OF GCM......................................................................................................................................7 | | | 5.1 | 5.1 | BLOCK CIPHER ............................................................................................................................................7 | | | 5.2 | 5.2 | TWO GCMFUNCTIONS ...............................................................................................................................7 | | | 5.2.1 | 5.2.1 | Authenticated Encryption Function .......................................................................................................8 | | | 5.2.2 | 5.2.2 | Authenticated Decryption Function.......................................................................................................9 | | | 5.3 | 5.3 | PRIMITIVES FOR CONFIDENTIALITY AND AUTHENTICATION........................................................................9 | | | 6 MATHEMATICAL COMPONENTS OF GCM...........................................................................................10 | 6 MATHEMATICAL COMPONENTS OF GCM...........................................................................................10 | 6 MATHEMATICAL COMPONENTS OF GCM...........................................................................................10 | | |"}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC", "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 Guide to Secure Web Services:\n\n| Background to Web Services and Their Relationship to Security..............................2-1 | Background to Web Services and Their Relationship to Security..............................2-1 | | | 2.1 | Introducing Web Services........................................................................................2-1 | Introducing Web Services........................................................................................2-1 | | | | 2.1.1 | Web Service Discovery ................................................................................2-1 | | | | 2.1.2 | Web Service Messaging...............................................................................2-2 | | | | 2.1.3 | Web Portals..................................................................................................2-3 | | | | 2.1.4 | Web Service Roles, Modes, and Properties.................................................2-3 | | | | 2.1.5 | Coordination: Orchestration and Choreography...........................................2-5 | | | 2.2 | Elements of Security................................................................................................2-7 | Elements of Security................................................................................................2-7 | | | 2.3 | Web Services Security Dimensions.........................................................................2-8 | Web Services Security Dimensions.........................................................................2-8 | | | | 2.3.1 | Secure Messaging........................................................................................2-8 | | | | 2.3.2 | Protecting Resources ...................................................................................2-8 | | | | 2.3.3 | Negotiation of Contracts...............................................................................2-9 | | | | 2.3.4 | Trust Relationships.....................................................................................2-10 | | | | 2.3.5 | Requirements for Secure Software | ............................................................2-11 | | | Meeting | the Requirements for Securing Web Services .........................................2-11 | | | 2.4 | 2.4.1 | Secure Web Service Standards Stack .......................................................2-11 | | | | 2.4.2 | Relationship of Web Service Security Requirements to Standards............2-13 | | | 2.5 | Core Services ........................................................................................................2-13"}], "metadata": {"source": "Guide to Secure Web Services", "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 Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements:\n\n| Date | Type | Change | Page Number | |-----------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | 1/20/2016 | Editorial | Changed the revision from '3' to '4' | cover page, i, ii | | | Editorial | Added new author: 'Dragos Prisaca' | cover page, i | | | Editorial | Changed secretary name to 'Penny Pritzker, Secretary' | i | | | Editorial | Changed the date of the document | i | | | Substantive | Changed abstract from 'This report defines the requirements and associated test procedures necessary for products to achieve one or more Security Content Automation Protocol (SCAP) validations.' to 'This report defines the requirements and associated test procedures necessary for products or modules to achieve one or more Security Content Automation Protocol (SCAP) validations.' | iii | | | Editorial | Added keywords 'SCAP validated products; SCAP validated modules' | iii | | | Editorial | Updated the Acknowledgements section | iv | | | Substantive | Changed 'SCAP Product' to 'SCAP product and module' in the Audience section | iv | | | Substantive | Changed the Trademark Information section from 'Windows XP, Windows Vista, and Windows 7 are registered trademarks of Microsoft Corporation.' to 'Windows® operating"}], "metadata": {"source": "Security Content Automation Protocol (SCAP) Version 1.2 Validation Program Test Requirements", "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 Recommendation for Block Cipher Modes of Operation_ Three Variants of Ciphertext Stealing for CBC Mode provide?"}, {"role": "assistant", "content": "Addendum to NIST Special Publication 800-38A October, 2010\n\n\n\nRecommendation for Block Cipher Modes of Operation: Three Variants of Ciphertext Stealing for CBC Mode\n\nMorris Dworkin\n\n## C O M P U T E R S E C U R I T Y\n\nAddendum to NIST Special Publication 800-38A\n\n## Recommendation for Block Cipher Modes of Operation: Three Variants of Ciphertext Stealing for CBC Mode\n\nMorris Dworkin\n\n## C O M P U T E R S E C U R I T Y\n\nComputer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930\n\nOctober 2010\n\n\n\nU.S. Department of Commerce\n\nGary Locke, Secretary\n\nNational Institute of Standards and Technology Patrick Gallagher, Director\n\n## Reports on Information Security 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 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. Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Three Variants of Ciphertext Stealing for CBC Mode", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\n\nare supported by an infrastructure for providing application services, such as service mesh. Both of these components are usually hosted on a container orchestration and resource management platform.\nIn this architecture, the entire set of source code involved in the application environment can be divided into five code types: 1) application code (which embodies the application logic), 2) application services code (for services such as session establishment, network connection, etc.), 3) infrastructure as code (for provisioning and configuring computing, networking, and storage resources), 4) policy as code (for defining runtime policies such as zero trust expressed as a declarative code), 5) and observability as code (for the continuous monitoring of an application runtime state). Due to security, business competitiveness, and the inherent structure of loosely coupled application components, this class of applications needs a different development, deployment, and runtime paradigm. DevSecOps (consisting of acronyms for Development, Security, and Operations, respectively) has been found to be a facilitating paradigm for these applications with primitives such as continuous integration, continuous delivery, and continuous deployment (CI/CD) pipelines. These pipelines are workflows for taking the developer's source code through various stages, such as building, testing, packaging, deployment, and operations supported by automated tools with feedback mechanisms. The objective of this document is to provide guidance for the implementation of DevSecOps primitives for cloud-native applications with the architecture and code types described above. The benefits of this approach for high security assurance and for enabling continuous authority to operate (C-ATO) are also discussed."}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "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\n.g., encryption) which require limited human interaction, particularly with users, education and awareness addresses the human-in-the-loop and so depends, in large part, on human-factors for efficacy.\nAll three teams specifically considered how their designs could be 'easiest' for users to use, understand, and be most accessible. Teams 1 and 3 incorporated gamification and other interactive elements to encourage users to pursue cybersecurity topics. For example, Team 3 attempted to gamify the pursuit of cybersecurity knowledge relative to the product by building out 'levels' of concepts that build upon each other so that users could 'level up' at their pace. Understanding and encouraging cybersecurity engagement has been a focus of research for the SOUPS community [8][9][10][11][12][13], and so the teams brought the insights from that research to the practical tasks of the Design-A-Thon. The contextual nature of cybersecurity education and awareness approaches was apparent when two teams (i.e., Teams 2 and 3) selected the same product but developed different approaches and focused on different aspects of the design. Teams 2 and 3 homed in on different information that may be useful at different times during the product's lifecycle. In one case, Team 2 focused on ensuring information was at users' fingertips, particularly when support was needed. In the other case, Team 3 considered how individuals could be encouraged to engage on cybersecurity education and awareness outside of times they needed support, landing on gamification elements. Research shows that gamification of cybersecurity education and awareness can drive engagement for individuals around the subject [14], but for IoT products, gamification elements should not get in the way when users need support or specific information."}], "metadata": {"source": "Report on the Design-A-Thon_ Designing Effective and Accessible Approaches for Digital Product Cybersecurity Education and Awareness", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to 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 Access Control?"}, {"role": "assistant", "content": "According to Annual Report 2018_ NIST_ITL Cybersecurity Program:\n\n- The Nation should set an ambitious vision and action plan-of-attack to 'prepare, grow, and sustain a national cybersecurity workforce that safeguards and promotes America's national security and economic prosperity.'\n- The Federal Government should lead in launching a high-profile national Call to Action to draw attention to and mobilize public and private sector resources to address cybersecurity workforce needs. - The Administration should focus on and recommend long-term authorization and sufficient appropriations for high-quality, effective cybersecurity education and workforce development programs in its budget proposals in order to grow and sustain the cybersecurity workforce. - Federal departments and agencies must move quickly to address major needs relating to recruiting, developing, and retaining cybersecurity employees and continue to implement the Federal Cybersecurity Workforce Strategy 43 and the Federal Cybersecurity Workforce Assessment Act of 2015 (FCWAA). 44\n- The private and public sectors need to transform, elevate, and sustain the learning environment to grow a dynamic and diverse cybersecurity workforce. - The private and public sectors need to align education and training with employers' cybersecurity workforce needs, improve coordination, and prepare individuals for lifelong careers. - The private and public sectors need to establish and leverage measures that demonstrate the effectiveness and impact of cybersecurity workforce investments."}], "metadata": {"source": "Annual Report 2018_ NIST_ITL Cybersecurity Program", "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 Hardware Security Failure Scenarios_ Potential Hardware Weaknesses provide? (Part 5)"}, {"role": "assistant", "content": "..........9 |\n| 3. Technical Approach......................................................................................................................10 |\n| 3.1.1.\nDetermining How Weaknesses Occur........................................................................................10 |\n| 3.1.2. Determining Where Weaknesses Occur.....................................................................................10 |\n| 3.1.3. Determining What Damage Weaknesses Allow.........................................................................10 |\n| 4. Hardware Security Failure Scenarios.............................................................................................14 |\n| 5. Categories of Hardware Design Weaknesses .................................................................................33 |\n\n| 6. Comparison With Software Weaknesses.......................................................................................46 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 7. Software Assurance Trends Categories..........................................................................................50 |\n| 8. Conclusion ...................................................................................................................................53 |\n| References.......................................................................................................................................54 |\n| Appendix A. List of Symbols, Abbreviations, and Acronyms...............................................................65 |\n| Appendix B."}], "metadata": {"source": "Hardware Security Failure Scenarios_ Potential Hardware Weaknesses", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Managing Information Security Risk_ Organization, Mission, and Information System View:\n\nSupplemental Guidance: Organizations can respond to risk in a variety of ways. These include: (i) risk acceptance; (ii) risk avoidance; (iii) risk mitigation; (iv) risk sharing; (v) risk transfer; or (vi) a combination of the above. A course of action is a time-phased or situation-dependent combination of risk response measures. For example, in an emergency situation, organizations might accept the risk associated with unfiltered connection to an external communications provider for a limited time; then avoid risk by cutting the connection; mitigate risk in the near-term by applying security controls to search for malware or evidence of unauthorized access to information that occurred during the period of unfiltered connection; and finally mitigate risk long-term by applying controls to handle such connections more securely. Supplemental Guidance: The evaluation of alternative courses of action can include: (i) the expected effectiveness in achieving desired risk response (and how effectiveness is measured and monitored); and (ii) anticipated feasibility of implementation, including, for example, mission/business impact, political, legal, social, financial, technical, and economic considerations. Economic considerations include costs throughout the expected period of time during which the course of action is followed (e.g., cost of procurement, integration into organizational processes at Tier 1 and/or Tier 2, information systems at Tier 3, training, and maintenance). During the evaluation of alternative courses of action, trade-offs can be made explicit between near-term gains in mission/business effectiveness or efficiency and long-term risk of mission/business harm due to compromise of information or information systems that are providing this nearterm benefit."}], "metadata": {"source": "Managing Information Security Risk_ Organization, Mission, and Information System View", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Random Bit Generator (RBG) Constructions:\n\n-------------------------------------------------------------------------|\n| [SP_800-38B] | Dworkin MJ (2005) Recommendation for Block Cipher Modes of Operation: the CMAC Mode for Authentication.\n(National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-38B, Includes updates as of October 6, 2016. https://doi.org/10.6028/NIST.SP.800-38B |\n| [SP_800-90A] | Barker EB, Kelsey JM (2015) Recommendation for Random Number Generation Using Deterministic Random Bit Generators. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-90Ar1. https://doi.org/10.6028/NIST.SP.800- |\n| [SP_800-90B] | 90Ar1 Sönmez Turan M, Barker EB, Kelsey JM, McKay KA, Baish ML, Boyle M (2018) Recommendation for the Entropy Sources Used for Random Bit Generation. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-90B. |\n| [SP_800_224] | Sönmez Turan M, Brandão LTAN (20 24) Keyed-Hash Message Authentication Code (HMAC): Specification of HMAC and Recommendations for Message Authentication. (National Institute of Standards and Technology, Gaithersburg, MD), NIST Special Publication (SP) NIST SP 800-224 ipd . https://doi.org/10.6028/ NIST.SP.800-22 4.ipd |\n| [SP800_90WebSite] | National Institute of Standards and Technology (2025) Random Bit Generation [SP 800-90 Project]. Available at https://csrc.nist.gov/Projects/random-bit-generation/sp-800 -90-updates |"}], "metadata": {"source": "Recommendation for Random Bit Generator (RBG) Constructions", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines:\n\n3.6.\n\n3.6. Redress\nDesigning services that support a wide range of populations requires processes to\nadjudicate issues and provide redress4\n as warranted. Service failures, disputes, and\nother issues tend to arise as part of normal operations, and their impacts can vary\nbroadly, from minor inconveniences to major disruptions or damage. Furthermore,\nthe same issue experienced by one person or community as an inconvenience can have\ndisproportionately damaging impacts on other individuals and communities.\n\nauthentication intent\nThe process of confirming the claimant’s intent to authenticate or reauthenticate by\nrequiring user intervention in the authentication flow. Some authenticators (e.g., OTPs)\nestablish authentication intent as part of their operation. Others require a specific step\nto establish intent, such as pressing a button. Authentication intent is a countermeasure\nagainst malware at the endpoint as a proxy for authenticating an attacker without the\nsubscriber’s knowledge."}], "metadata": {"source": "Digital Identity Guidelines", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Engineering Trustworthy Secure 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.\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. ## NIST Technical Series Policies\n\nCopyright, Fair Use, and Licensing Statements NIST Technical Series Publication Identifier Syntax\n\n## Publication History\n\nApproved by the NIST Editorial Review Board on 2022-11-08 Supersedes NIST SP 800-160 Vol. 1 (Nov. 2016; updated 2018-03-21) https://doi.org/10.6028/NIST.SP.800-160v1\n\n## How to Cite this NIST Technical Series Publication:\n\nRoss R, McEvilley M, Winstead M (2022) Engineering Trustworthy Secure Systems."}], "metadata": {"source": "Engineering Trustworthy Secure Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does Security Analysis of First Responder Mobile and Wearable Devices provide?"}, {"role": "assistant", "content": "## NISTIR 8196\n\n## Security Analysis of First Responder Mobile and Wearable Devices\n\nJoshua M. Franklin Gema Howell Scott Ledgerwood Jaydee L. Griffith\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8196\n\n\n\n## NISTIR 8196\n\n## Security Analysis of First Responder Mobile and Wearable Devices\n\nJoshua M. Franklin* Gema Howell Applied Cybersecurity Division Information Technology Laboratory\n\nScott Ledgerwood Public Safety Communications Research Division Communications Technology Laboratory\n\nJaydee L. Griffith Institute for Telecommunication Sciences National Telecommunications and Information Administration\n\n* Former employee; all work for this\n\nPublication was done while at NIST\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8196\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 8196 75 pages (May 2020)\n\n## This publication is available free of charge from: https://doi.org/10.6028/NIST.IR.8196\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by NIST, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. There may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications."}], "metadata": {"source": "Security Analysis of First Responder Mobile and Wearable Devices", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products:\n\nProduct criteria are recommended to apply to the IoT product overall, as well as to each individual IoT product component (e.g., IoT device, backend, companion app), as appropriate. 6 A scheme owner has flexibility in adapting the product criteria and determining appropriate supporting evidence. Though NIST recommends that all criteria apply to every IoT product, some components may not be able or need to support all criteria. That might be the case due to product risk considerations, product development (e.g., cybersecurity tasks delegated via contracts and supply chain), nature of the components to form the product (e.g., backends may be highly distributed), or limitations of IoT components (e.g., devices may be constrained, companion software apps may have limited access and functionality). - iv. Consideration of the known risks related to the IoT product and known potential misuses. - v. Secure software development and supply chain practices used. - vi. Accreditation, certification, and/or evaluation results for cybersecurityrelated practices. - vii. The ease of installation and maintenance of the IoT product by a customer (i.e., the usability of the product [ISO9241]). - e. Maintenance requirements for the IoT product, for example :\n- i. Cybersecurity maintenance expectations and associated instructions or procedures (e.g., vulnerability/patch management plan). - ii. How the IoT product developer identifies authorized supporting parties who can perform maintenance activities (e.g., authorized repair centers). - iii. Cybersecurity considerations of the maintenance process (e.g., how customer data unrelated to the maintenance process remains confidential even from maintainers). - f. The secure system lifecycle policies and processes associated with the IoT product, including :\n- i. Steps taken during development to ensure the IoT product and its product components are free of any known, exploitable vulnerabilities. - ii."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to Fiscal Year 2023 Cybersecurity and Privacy Annual Report:\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": "Fiscal Year 2023 Cybersecurity and Privacy Annual Report", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Security Architecture Design Process for Health Information Exchanges (HIEs):\n\n| Capstone Policy Drivers | Entities Affected | Enabling Services Affected | Comment | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | American Recovery and Reinvestment Act of 2009, Public Law 111-5 (ARRA) | HIPAA-covered entities and their business associates; PHR vendors; and possibly other health-related organizations | Risk Assessment; Secured Communication Channel; Document Confidentiality | Requires the Office of the National Coordinator to establish two panels on health IT; holds business associates of HIPAA-covered entities directly responsible for certain standards of the Privacy and Security Rules; requires certain HIPAA covered entities to notify individuals who have been affected by breaches of their health information."}], "metadata": {"source": "Security Architecture Design Process for Health Information Exchanges (HIEs)", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Media Protection?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”:\n\n- Risks posed by unsupported \"zombie devices\" that lack updates or patches, compensating controls to address the additional risk from this status, and continue to operate on the network, creating security blind spots;\n- Lack of secure disposal for decommissioned IoT products and product components to prevent exploitation of sensitive data or credentials as a weakness in the IoT ecosystem;\n- Absence of modular replacement strategies for IoT products in long-term use cases such as industrial or healthcare settings where lifespans for products may be long;\n- Concerns raised regarding replay attacks during ownership transitions that can make the prior owner's data accessible to the new owner;\n- Potential for unexpected or nefarious activity from IoT products such as collecting unintended data continues to impede trust in IoT;\n- Practical complexities of integrating IoT products into diverse ecosystems; and\n- Technical challenges to supporting post-quantum cryptography for most IoT products, particularly on IoT devices."}], "metadata": {"source": "Workshop Summary Report for “Workshop on Foundational Cybersecurity Activities for IoT Device Manufacturers”", "cmmc_level": "1", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”:\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": "Workshop Summary Report for “Building on the NIST Foundations_ Next Steps in IoT Cybersecurity”", "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 Conformance Assessment of Transport Layer Security Implementations provide?"}, {"role": "assistant", "content": "\n\nE\n\np\n\np\n\n## Conformance Assessment of Transport Layer Security Implementations\n\n-Qe100 .056\n\n## Wayne A. Jansen Editor\n\nU.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Gaithersburg, MD 20899\n\n\n\n## Conformance Assessment of Transport Layer Security Implementations\n\n## Wayne A. Jansen Editor\n\nU.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Gaithersburg, MD 20899\n\n[December 1993\n\n\n\nU.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary\n\nTECHNOLOGY ADMINISTRATION Mary L Good, Linder Secretary for Technology\n\nNATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director\n\n## ABSTRACT\n\nThis paper presents a framework for evaluating conformance of a protocol implementation to the Security Protocol at layer 4 (SP4) standard. SP4 is one element of the Secure Data Network System (SDNS) architecture, used to provide security services at the Transport layer of the Open System Interconnection (OSI) reference model. SP4 also forms the basis of the ISO standard for the OSI Transport Layer Security Protocol (TLSP). Therefore, with few exceptions, the findings of the paper are applicable to TLSP. The paper explores the relationship between conformance assessment, interoperability assessment, and security evaluation of security protocols. The OSI conformance testing methodology and framework is reviewed, and a strategy is given for applying this methodology to SP4 implementations. Keywords: OSI, Lower Layer Security Protocols, Conformance Testing, Security Evaluation, Interoperability Testing, SP4. ## TABLE OF CONTENTS\n\n| 1. | INTRODUCTION | INTRODUCTION | 1 |\n|------------|-----------------------------------------------|-----------------------------------------------|-----|\n| 2."}], "metadata": {"source": "Conformance Assessment of Transport Layer Security Implementations", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings provide? (Part 5)"}, {"role": "assistant", "content": "| Defining the Internet of Things........................................................................\n3 |\n| | 2.2 | IoT Cybersecurity and Privacy Risks .............................................................. 3 |\n| | 2.3 | IoT-Specific Risks ..........................................................................................."}], "metadata": {"source": "Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\nSC-13 | For the protection of keys and metadata used to protect data at the Moderate impact-level, a Federal CKMS shall employ cryptographic modules validated at FIPS 140 security level 3 or higher.\n|\n| PR:2.13 | SC-13 | For the protection of keys and metadata used to protect data at the High impact-level, a Federal CKMS shall employ cryptographic modules validated at FIPS 140 physical security level 4, and all other areas at security levels 3 or higher. |\n| PA:2.2 | | A Federal CKMS should assure that all its cryptographic modules are protected against invasive and non-invasive attacks. |"}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.5 (NIST 3.2.5)?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\n3.2.5 Availability... 3.2.5 discuss pre-RSN IEEE 802. 3.2.5 Availability\n\nIndividuals who do not have physical access to the WLAN infrastructure can cause a denial of service for the WLAN."}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "cmmc_level": "all", "nist_control": "3.2.5", "cmmc_practice_id": "AT.L2-3.2.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to 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 guidance does Recommendation for Cryptographic Key Generation provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-133 Revision 2\n\n## Recommendation for Cryptographic Key Generation\n\nElaine Barker Allen Roginsky Richard Davis\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-133r2\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-133 Revision 2\n\n## Recommendation for Cryptographic Key Generation\n\nElaine Barker Allen Roginsky Computer Security Division Information Technology Laboratory\n\nRichard Davis National Security Agency\n\nThis publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-133r2\n\nJune 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## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official."}], "metadata": {"source": "Recommendation for Cryptographic Key Generation", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 U.S. Department of Energy Risk Assessment Methodology:\n\n|\n| | 2. | Risk Assessment: Computer Based Tools | |\n| | 3.\n| Threats and Vulnerabilities | |\n| | 4. | Countermeasures: Equipment and Technologies | |\n| | 5. | Countermeasures: Procedures | |\n| | 6. | Networks | |\n| | 7. | Viruses and Other Related Threats | |\n| | 8. | Risk Management | |\n| | 9. | Certification and Accreditation | |\n| | 10. | Other U.S. Government Computer Security Publications | |"}], "metadata": {"source": "U.S. Department of Energy Risk Assessment Methodology", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guide to Using Vulnerability Naming Schemes provide? (Part 4)"}, {"role": "assistant", "content": "............................... 2 2.1 Common Vulnerabilities and Exposures (CVE) 2.2 Common Configuration Enumeration (CCE) 5...........................................................3 |\n| 1.1 1.2 2.\n| Authority....................................................................................................................1 Purpose and Scope...................................................................................................1 |\n| 1.3 | Audience ...................................................................................................................1 |\n| 1.4 | Document Structure ..................................................................................................1 |\n| | .........................................................2 |\n| 3. | 4 |\n| | Recommendations for End-User Organizations ............................................................"}], "metadata": {"source": "Guide to Using Vulnerability Naming Schemes", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 3}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\nNISTIR 8183 Revision 1 updates the Manufacturing Profile to include the sub-category enhancements established in NIST Framework for Improving Critical Infrastructure Cybersecurity Version 1.1. These updates include managing cybersecurity within the supply chain, self-assessing cybersecurity risk, vulnerability disclosure, system integrity, and more comprehensive controls for identity management."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Automation Support for Security Control Assessments_ Volume 1_ Overview:\n\n3.1.3 Simplifies Understanding of the Overall Protection Process... 3.1.3 Simplifies Understanding of the Overall Protection Process\n\nIt is a difficult task to achieve detailed understanding of hundreds of individual security control items, thus, defining security capabilities may simplify how the protection problem is viewed conceptually."}], "metadata": {"source": "Automation Support for Security Control Assessments_ Volume 1_ Overview", "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 guidance does Application Container Security Guide provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-190\n\n## アプリケーションコンテナセキュリティガイド\n\nMurugiah Souppaya John Morello Karen Scarfone\n\n本書は、以下より無料で利用可能である： https://doi.org/10.6028/NIST.SP.800-190\n\n## C O M P U T E R S E C U R I T Y\n\nこの文書は以下の団体によって翻訳監修されています\n\n\n\n本文書は、原典に沿ってできるだけ忠実に翻訳するよう努めていますが、完全性、 正確性を保証するものではありません。\n\n翻訳監修主体は、本文書に記載されている情報より生じる損失または損害に対し て、いかなる人物あるいは団体についても責任を負うものではありません。\n\n\n\n## NIST Special Publication 800-190 アプリケーションコンテナセキュリティガイド\n\nMurugiah Souppaya Computer Security Division Information Technology Laboratory\n\nJohn Morello Twistlock Baton Rouge, Louisiana\n\nKaren Scarfone Scarfone Cybersecurity Clifton, Virginia\n\n本書は、以下より無料で利用可能である： https://doi.org/10.6028/NIST.SP.800-190\n\n2017 年 9 月\n\n\n\n米国商務省 Wilbur L. Ross, Jr., Secretary\n\n米国国立標準技術研究所\n\nKent Rochford, Acting Under Secretary of Commerce for Standards and Technology and Acting Director\n\n## 発行機関\n\n本文書は、連邦情報セキュリティ近代化法（ FISMA ： Federal Information Security Modernization Act ） 2014 年、合 衆国法典（ U.S. Code ）第 44 編 第 3541 条 等、および公法（ P.L. ） 113 条 -283 条に基づく法的責任により、米国国 立標準技術研究所（ NIST ： National Institute of Standards and Technology 、以下、 NIST と称す）によって作成され た。 NIST は、連邦政府情報システムの最低限の要求事項を含む情報セキュリティ標準及びガイドラインを策定する 責務があるが、このような標準及びガイドラインを国家安全保障システムに適用するには、このようなシステムに ついての政策的権限を有する適切な連邦政府機関の明確な承認が必要となる。このガイドラインは、行政管理予算 庁（ OMB ： Office of Management and Budget ）による通達（ Circular ） A-130 号の要求事項と一致している。\n\n本文書のいかなる内容も、商務長官が法的権限に基づき連邦政府に対して義務及び拘束力を与えた標準及びガイド ラインを否定するものではない、また、これらのガイドラインは、商務長官、行政管理予算局長、または他のすべ ての連邦政府当局者の既存の権威に変更を加えたり、これらに取って代わるものと解釈したりしてはならない。本 文書は、非政府組織が自由に使用することもでき、米国における著作権の対象ではないが、 NIST に帰属する。\n\nNational Institute of Standards and Technology Special Publication 800-190 Natl. Inst. Stand. Technol. Spec. Publ."}], "metadata": {"source": "Application Container Security Guide", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Federation and Assertions:\n\n| 1. Introduction . . . . . . . . . . . . . | 1. Introduction . . . . . . . . . . . . . | 1. Introduction . . . . . . . . . . . . . |\n|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|\n| | 1.1. . . . . . . . . . . . . . . . | Notations . . . . . . . . . . . . . . . . . . . 1 |\n| | 1.1.1. Cryptographic Terminology . | . . . . . . . . . . . . . . . . . . . 2 |\n| 1.2. | Document Structure . . . . . . . . . | . . . . . . . . . . . . . . . . . . . 3 |\n| 2. Federation Assurance Level (FAL) . . . . . . . . . . . . . . . . . . . . . . . . 4 | 2. Federation Assurance Level (FAL) . . . . . . . . . . . . . . . . . . . . . . . . 4 | 2. Federation Assurance Level (FAL) . . . . . . . . . . . . . . . . . . . . . . . . 4 |\n| | 2.1. . . . . | Common FAL Requirements . . . . . . . . . . . . . . . . . . . . 5 |\n| | 2.2. | Federation Assurance Level 1 (FAL1) . . . . . . . . . . . . . . . . . . . . 6 |\n| | 2.3. | Federation Assurance Level 2 (FAL2) . . . . . . . . . . . . . . . . . . . . 6 |\n| | 2.4. | Federation Assurance Level 3 (FAL3) . . . . . . . . . . . . . . . . . . . . 7 |\n| 2.5."}], "metadata": {"source": "Digital Identity Guidelines_ Federation and Assertions", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N provide?"}, {"role": "assistant", "content": "## NIST Special Publication 800-178\n\n## A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications\n\nExtensible Access Control Markup Language (XACML) and Next Generation Access Control (NGAC)\n\nDavid Ferraiolo Ramaswamy Chandramouli Vincent Hu Rick Kuhn\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-178\n\n## C O M P U T E R S E C U R I T Y\n\n\n\n## NIST Special Publication 800-178\n\n## A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications\n\nExtensible Access Control Markup Language (XACML) and Next Generation Access Control (NGAC)\n\nDavid Ferraiolo Ramaswamy Chandramouli Vincent Hu Rick Kuhn Computer Security Division Information Technology Laboratory\n\nThis publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-178\n\nOcto ber 2016\n\n\n\nU.S. Department of Commerce Penny Pritzker, Secretary\n\nNational Institute of Standards and Technology Willie May, Under Secretary of Commerce for Standards and Technology and Director\n\n## Authority\n\nThis publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3551 et seq. , Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority."}], "metadata": {"source": "A Comparison of Attribute Based Access Control (ABAC) Standards for Data Service Applications_ Extensible Access Control Markup Language (XACML) and N", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to LTE Security:\n\n| Document Structure........................................................................................\n| 6 |\n| | 1.3 | Document Conventions................................................................................... | 7 |\n| 2 | Overview of LTE Technology................................................................................8 | Overview of LTE Technology................................................................................8 | |\n| | 2.1 | Evolution of 3GPP Standards | ........................................................................."}], "metadata": {"source": "Guide to LTE Security", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does The NIST Definition of Cloud Computing provide? (Part 5)"}, {"role": "assistant", "content": "and network bandwidth. - Rapid elasticity. Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand.\nTo the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time. - Measured service. Cloud systems automatically control and optimize resource use by leveraging a metering capability 1 at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. ## Service Models:\n\nSoftware as a Service (SaaS). The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure 2 . The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based email), or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited userspecific application configuration settings. Platform as a Service (PaaS) . The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming\n\n1 Typically this is done on a pay-per-use or charge-per-use basis. 2 A cloud infrastructure is the collection of hardware and software that enables the five essential characteristics of cloud computing. The cloud infrastructure can be viewed as containing both a physical layer and an abstraction layer."}], "metadata": {"source": "The NIST Definition of Cloud Computing", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters:\n\n3.2.2. 3.2.2), or a twisted Edwards curve (Section 3. 3.2.2."}], "metadata": {"source": "Recommendations for Discrete Logarithm-based Cryptography_ Elliptic Curve Domain Parameters", "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 Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines provide? (Part 2)"}, {"role": "assistant", "content": "cessing Standards Task Group 15. This task group was established by the Department of Commerce within its National Bureau of Standards to develop standards and guidelines in Computer Systems Security.\nSpecial recognition should go to the following participants of the task group which has comnended their efforts in preparing this document: Margaret W. Alter, Office of Federal Management Policy, General Services Administration; Philip H. Diamond, Department of Data Management, Veterans Administration; and Robert H. Follett, Office of Federal Business Relations, International Business Machines Corporation. Any comments you have concerning this index or its use are welcomed. Please forward them to the Associate Director for ADP Standards, Institute for Computer Sciences and Technology, National Bureau of Standards, Washington, D.C. 20234, or telephone (301) 921-3157. * Privacy Act of 1974; Public Law 93-579. ** Privacy Act Implementation Guidelines and Responsibilities, Office of Management and Budget, dated July 1, 1975 and published in the Federal Register on July 9, 1975 (40 FR 28947-28978). CO Ui 3 H u < u < > U OS I-t cu Q S O 00 s: -CO CTl C/) Q r-t < -J O ^ 3 UJ < E H O S O X a; Q 2 O 1-1 Ui > u Q cu\n\nc\n\n4J\n\n£\n\n43\n\n^1\n\n•H\n\n3\n\nCT\n\n43\n\nca\n\nu\n\n•H\n\nc\n\nu\n\nX\n\n43\n\n•H\n\n| | m ."}], "metadata": {"source": "Index of Automated System Design Requirements as Derived from the OMB Privacy Act Implementation Guidelines", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies:\n\ns for an other than authorized purposes, have access or potential |\n\n| | access to sensitive information, whether physical or electronic.\n|\n|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Categorization | The process of determining the security category for information or an information system. Security categorization methodologies are described in CNSS Instruction 1253 for national security systems and in FIPS Publication 199 for other than national security systems. |\n| Ciphertext | Data in its encrypted form. |\n| Confidentiality | The property that sensitive information is not disclosed to unauthorized entities. |\n| Critical Infrastructure | The essential services that support a society and serve as the backbone for the society's economy, security and health. |\n| Cryptographic algorithm | A well-defined computational procedure that takes variable inputs, including a cryptographic key (if applicable), and produces an output. |\n| Cryptographic Key | A parameter used in conjunction with a cryptographic algorithm that determines its operation in such a way that an entity with knowledge of the key can reproduce or reverse the operation, while an entity without knowledge of the key cannot. |\n| Cryptography | The science of information hiding and verification. It includes the protocols, algorithms and methodologies to securely and consistently prevent unauthorized access to sensitive information and enable verifiability of the information."}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies", "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 Practical Combinatorial Testing provide? (Part 5)"}, {"role": "assistant", "content": "| 12 | | 3.1 | 3.1 | Simple Application Platform Example..............................................................12 | | | 3.2 | 3.2 | Smart Phone Application Example....................................................................14 | | | 3.3 | 3.3 | Cost and Practical Considerations | .....................................................................16 | | 3.4 | 3.4 | Chapter Summary | ..............................................................................................17 | | 4 | 4 | INPUT PARAMETER TESTING ................................................................"}], "metadata": {"source": "Practical Combinatorial Testing", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 User's Guide to Telework and Bring Your Own Device (BYOD) Security:\n\nchecking email from a kiosk computer at a hotel or from a friend's mobile phone. However, teleworkers typically do not know if such devices have been secured properly or if they have been compromised.\nConsequently, a teleworker could use a device infected with malware that steals their information (e.g., passwords, email messages, and other sensitive data). Many organizations either prohibit unknown devices from being used for remote access or permit use only by having the teleworker first restart the PC with special removable media inserted so that the PC will reboot into a secure environment for telework purposes."}], "metadata": {"source": "User's Guide to Telework and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012:\n\nCryptographic techniques are potentially very useful to improve the security and privacy properties of IMDs through stronger authentication protocols and (confidentiality and integrity) protected communications over wireless channels. However, since IMDs operate in very constrained environments (such as device size, cost, and power availability,) traditional cryptographic techniques and protocols may be inappropriate. More compatible cryptographic suites and protocols need to be devised for use on IMDs and applied in a very selective manner to optimize the security protection from these power intensive operations. The body of research conducted for cryptography for sensor networks are directly applicable [8] to applying cryptographic techniques to IMDs.\n\n## A. Equipment Control and Recipe Integrity\n\n## B. Process Data Integrity"}], "metadata": {"source": "Proceedings of the Cybersecurity in Cyber-Physical Systems Workshop, April 23-24, 2012", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile:\n\n| RS.IM | Improvements | | RC | Recover | RC.RP | Recovery Planning | | RC | Recover | RC.IM | Improvements | | RC | Recover | RC.CO | Communications |"}], "metadata": {"source": "Cybersecurity Framework Manufacturing 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 Level 3 require for Awareness and Training?"}, {"role": "assistant", "content": "According to Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171:\n\n............................................ 5 |\n| 2.1 DEVELOPMENTAPPROACH ......................................................................................................\n| 5 |\n| 2.2 ORGANIZATIONANDSTRUCTURE | ............................................................................................. 7 |\n| 2.3 FLEXIBLE APPLICATION | ............................................................................................................. 9 |\n| CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 | CHAPTER THREE THE REQUIREMENTS......................................................................................... 11 |\n| 3.1 ACCESSCONTROL | .................................................................................................................. 12 |\n| 3.2 AWARENESSANDTRAINING | ..................................................................................................."}], "metadata": {"source": "Enhanced Security Requirements for Protecting Controlled Unclassified Information_ A Supplement to NIST Special Publication 800-171", "cmmc_level": "3", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Minimum Security Requirements for Multi-User Operating Systems:\n\nor activity. (R)\n3. The system shall protect the security audit trail from unauthorized access. (R)\n- a. Maintenance and management of the security audit trail files shall require privilege. (R)\n- b.\nThe system should support an option to maintain the security audit trail data in encrypted format.' (A)"}], "metadata": {"source": "Minimum Security Requirements for Multi-User Operating 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 System and Services Acquisition?"}, {"role": "assistant", "content": "According to Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations:\n\nThe NIST Risk Management Framework (RMF), described in NIST Special Publication 800-37 Revision 1, Guide for Applying the Risk Management Framework to Federal Information Systems: a Security Life Cycle Approach, is a methodology for implementing risk management at the information systems tier. The RMF (depicted in Figure 2) identifies six distinct steps that provide a disciplined and structured process to integrate information security risk management activities into the system development life cycle. The RMF addresses security concerns of organizations related to the design, development, implementation, operation, and disposal of information systems and the environments in which those systems operate. The criteria for whether a security control is assurance- or functionality-related is based on the overall characteristics of the control. In general, assurance-related controls are controls that: (i) define processes, procedures, techniques, or methodologies for designing and developing information systems and system components; (ii) provide supporting operational processes including improving the quality of systems, components, or processes; (iii) produce security evidence from developmental or operational activities; (iv) determine security control effectiveness or risk; or (v) improve personnel skills, expertise, and understanding. Many organizations use well-known international information security standards as the basis or as a supplemental source of security controls for risk management. To aid in selection and comparison, SP 800-53 Rev. 4 provides mapping tables to provide organizations with a general indication of security control coverage with respect to ISO/IEC 27001, Information technologySecurity techniques-Information security management systems-Requirements and ISO/IEC 15408, Information technology -- Security techniques -- Evaluation criteria for IT security ."}], "metadata": {"source": "Summary of NIST SP 800-53, Revision 4_ Security and Privacy Controls for Federal Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3:\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": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.3", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.5 (NIST 3.1.5)?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n3.1.5. 3.1.5."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "nist_control": "3.1.5", "cmmc_practice_id": "AC.L2-3.1.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance provide? (Part 5)"}, {"role": "assistant", "content": "| 1.3 About the Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance...................................................................................................\n2 |\n| 2 Event Summary and Key Takeaways ...................................................................4 | 2 Event Summary and Key Takeaways ...................................................................4 |\n| | 2.1 Plenary Sessions ............................................................................................"}], "metadata": {"source": "Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\nIn working with the Office of Management and Budget to develop standards and guidelines\nrequired by FISMA, NIST consults with federal agencies, state, local, and tribal governments, and\nprivate sector organizations to improve information security and privacy, avoid unnecessary and\ncostly duplication of effort, and help ensure that its publications are complementary with the\nstandards and guidelines used for the protection of national security systems. In addition to a\ncomprehensive and transparent public review and comment process, NIST is engaged in a\ncollaborative partnership with the Office of Management and Budget, Office of the Director of\nNational Intelligence, Department of Defense, Committee on National Security Systems, Federal\nCIO Council, and Federal Privacy Council to establish a Risk Management Framework (RMF) for\ninformation security and privacy for the Federal Government. This common foundation provides\nthe Federal Government and their contractors with cost-effective, flexible, and consistent ways\nto manage security and privacy risks to organizational operations and assets, individuals, other\norganizations, and the Nation. The framework provides a basis for the reciprocal acceptance of\nsecurity and privacy control assessment evidence and authorization decisions and facilitates\ninformation sharing and collaboration. NIST continues to work with public and private sector\nentities to establish mappings and relationships between the standards and guidelines\ndeveloped by NIST and those developed by other organizations. NIST anticipates using these\nmappings and the gaps they identify to improve the control catalog. CHAPTER ONE INTRODUCTION ...................................................................................................... 1\n1.1 PURPOSE AND APPLICABILITY ..................................................................................................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Security Guidelines for Storage Infrastructure provide? (Part 5)"}, {"role": "assistant", "content": "ay; file storage service; block storage service; object storage service; storage virtualization; software-defined storage; hyper-converged storage; data protection; cloud storage; backup; replication.\n## Acknowledgements\n\nThe authors like to express their sincere thanks to NetApp, Dell EMC, Storage Networking Industry Association (SNIA), IEEE, Infinidat, and the Center for Cybersecurity Standards at NSA for their extensive, insightful feedback. Our special thanks to Yaniv Valik of Continuity Software for his valuable input during the writing of this document. ## Patent Disclosure Notice\n\nNOTICE: The Information Technology Laboratory (ITL) has requested that holders of patent claims whose use may be required for compliance with the guidance or requirements of this publication disclose such patent claims to ITL. However, holders of patents are not obligated to respond to ITL calls for patents and ITL has not undertaken a patent search in order to identify which, if any, patents may apply to this publication. As of the date of publication and following call(s) for the identification of patent claims whose use may be required for compliance with the guidance or requirements of this publication, no such patent claims have been identified to ITL. No representation is made or implied by ITL that licenses are not required to avoid patent infringement in the use of this publication. ## Executive Summary\n\nStorage, computing, and networking form the three fundamental building blocks of an information technology infrastructure. Just like computing and network technologies, storage technology has also evolved over the years. Higher capacity storage media and storage system architecture are the two fronts on which storage technology has evolved. The developments on the second front have enabled storage services to support many new and evolving computing use cases but have also introduced storage management complexity and many security challenges."}], "metadata": {"source": "Security Guidelines for Storage Infrastructure", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Foundations of a Security Policy for Use of the National Research and Educational Network:\n\n| 1 Introduction | 1 Introduction | 1 Introduction | 1 | |------------------------------------------------|----------------------------------------------------------|----------------------------------------------------------|-----| | 1.1 | | Background | 1 | | | 1.2 | Purpose and Scope of Report | 1 | | | 1.3 | Overview of Report | 2 | | 2 | Evolution of the NREN | Evolution of the NREN | 3 | | 2.1 | Introduction | Introduction | 3 | | 2.2 | Early DARPA Sponsorship | Early DARPA Sponsorship | 4 | | | 2.2.1 | National Science Foundation Sponsorship | 5 | | | 2.2.2 | Supercomputing Initiative | 5 | | | 2.2.3 | Development of a Higher Capacity Backbone | 5 | | | 2.2.4 | Experimental Gigabit Networks | 6 | | 2.3 | The Internet | The Internet | 7 | | 2.4 | Present Federal Interest and Initiatives | Present Federal Interest and Initiatives | 8 | | | 2.4.1 | Federal Councils, Committees and Information Offices | 8 | | | 2.4.2 | High Performance Computing and Communications Initiative | 9 | | | 2.4.3 | Mandate for a National Research and Educational Network | 9 | | | 2.4.4 | Pending Questions on General"}], "metadata": {"source": "Foundations of a Security Policy for Use of the National Research and Educational Network", "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 PS.L2-3.9.3 (NIST 3.9.3)?"}, {"role": "assistant", "content": "According to De-Identifying Government Datasets_ Techniques and Governance:\n\n3.9.3. 3.9.3."}], "metadata": {"source": "De-Identifying Government Datasets_ Techniques and Governance", "cmmc_level": "all", "nist_control": "3.9.3", "cmmc_practice_id": "PS.L2-3.9.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.4 (NIST 3.2.4)?"}, {"role": "assistant", "content": "According to An Introduction to Information Security:\n\n3.2.4 Penetration Testing\n\nPenetration testing can use many methods to attempt a system break-in."}], "metadata": {"source": "An Introduction to Information Security", "cmmc_level": "all", "nist_control": "3.2.4", "cmmc_practice_id": "AT.L2-3.2.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Recommended Criteria for Cybersecurity Labeling of Consumer Software provide? (Part 2)"}, {"role": "assistant", "content": "bersecurity 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.\nSubmit comments on this publication to:\n\nlabeling-eo@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). ## Acknowledgments\n\nThe authors of this document wish to thank all of those who provided input on this effortespecially those who attended our workshops, participated in one-on-one phone calls, and provided written comments on our draft. ## Audience\n\nThis document is intended for three primary audiences:\n\n1. Organizations which may be interested in implementing a labeling scheme for consumer software. 2. Organizations which produce or distribute consumer software and are interested in participating in future labeling programs. 3. Consumers who are interested in understanding a potential future labeling program. ## Document Conventions\n\nThe terms 'should' and 'should not' indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling of Consumer Software", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC:\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 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."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ Galois_Counter Mode (GCM) and GMAC", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\nThis report provides practical cybersecurity guidance for small-scale solar inverter implementations that are typically used in homes and small businesses. These guidelines are informed by a review of known smart-inverter vulnerabilities documented in the National Vulnerability Database (NVD), a review of information about known smart-inverter cyberattacks, and testing of five example smart inverters. The report also provides recommendations to smart-inverter manufacturers on the cybersecurity capabilities needed in their products to implement the seven guidelines. These recommendations build on the Internet of Things (IoT) cybersecurity capability baselines defined in NIST IR 8259A and IR 8259B by providing smartinverter-specific information for some of the baseline cybersecurity capabilities. | E.1.6. ISA/IEC 62443-2-1.......................................................................................................................33 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Appendix F. Smart Inverter Vulnerability Survey...............................................................................37 |\n| List of Tables |\n| Table 1."}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Guidelines for the Secure Deployment of IPv6:\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. The authors would like to acknowledge Tim Grance of NIST for his keen and insightful assistance and encouragement throughout the development of the document. The authors particularly want to thank Mark Carson, Doug Montgomery and Stephen Nightingale of NIST and Scott Hogg for their careful review and valuable contributions to improving the quality of this publication. | | 5.3.3 | Support for Multicast .................................................................................."}], "metadata": {"source": "Guidelines for the Secure Deployment of IPv6", "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 Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n....................................................................18 | |\n| 4.2.2.\n| Mobile Application Management............................................................................20 | |\n| 4.2.3. | Mobile Threat Defense...........................................................................................21 | |\n| 4.2.4. | Mobile App Vetting.................................................................................................22 | |\n| 4.2.5. | Virtual Mobile Infrastructure ...................................................................................22 | |\n| 4.2.6. | Application Wrapping.............................................................................................23 | |\n| 4.2.7. | Secure Containers.................................................................................................23 | |\n| | Recommended Mitigations and Countermeasures | ....................................................23 |\n| 4.3.1."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Recommendation for Stateful Hash-Based Signature Schemes:\n\n3.1.3 of [1]) shall be generated using the pseudorandom key generation method specified in Algorithm 10' in Section 7."}], "metadata": {"source": "Recommendation for Stateful Hash-Based Signature Schemes", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Ransomware Risk Management_ A Cybersecurity Framework Profile:\n\n| Category | Subcategory and Selected Informative References | Ransomware Application | |-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Identify | | | | Asset Management (ID.AM): The data, personnel, devices, systems, and facilities that enable the organization to achieve business purposes are identified and managed consistent with their relative importance to organizational objectives and the organization's risk strategy."}], "metadata": {"source": "Ransomware Risk Management_ A Cybersecurity Framework Profile", "cmmc_level": "all", "cmmc_domain": "Planning", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Notional Supply Chain Risk Management Practices for Federal Information Systems:\n\nnsequences throughout the supply chain and element life cycle. - g) Establish mechanisms and processes for checking and auditing unique identifications within the acquirer and integrator environments.\n- h) Document that integrator personnel are assigned appropriate roles throughout the system/element life cycle, regardless of personnel turnover, to ensure that the visibility of critical processes and elements is maintained."}], "metadata": {"source": "Notional Supply Chain Risk Management Practices for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i:\n\nNIST recommends that Federal agencies implement the following recommendations to assist in establishing and maintaining robust security for their IEEE 802.11i-based WLANs. Personnel responsible for their implementation and maintenance should read the corresponding sections of the document to ensure they have an adequate understanding of important related issues."}], "metadata": {"source": "Establishing Wireless Robust Security Networks_ A Guide to IEEE 802.11i", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines for Derived Personal Identity Verification (PIV) Credentials:\n\n## Guidelines for Derived Personal Identity Verification (PIV) Credentials\n\n## Guidelines for Derived Personal Identity Verification (PIV) Credentials\n\nThis recommendation provides technical guidelines for the implementation of standards-based, secure, reliable, interoperable public key infrastructure (PKI) based identity credentials that are issued by Federal departments and agencies to individuals who possess and prove control over a valid PIV Card. The scope of this document includes requirements for initial issuance and maintenance of these credentials, certificate policies and cryptographic specifications, technical specifications for permitted cryptographic token types and the command interfaces for the removable implementations of such cryptographic tokens."}], "metadata": {"source": "Guidelines for Derived Personal Identity Verification (PIV) Credentials", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Security Analysis of First Responder Mobile and Wearable Devices:\n\nWearable devices can also provide situational awareness through the data collected from the sensors, such as an individual's GPS location, heart rate, and other health data. This could be useful when, for instance, monitoring the status of firefighters responding to a fire emergency. If a firefighter's heart rate slows or stops, or if other tracked vital signs indicate a problem, the wearable can send a warning to the fire chief or Incident Commander with that firefighter's status and location. In contrast, wearable devices used by EMS responders can be used on both the emergency medical technician (EMT) and on patients. A vital sign wearable can report blood pressure/blood sugar levels and other vital signs back to the hospital where a doctor can provide real-time assistance to the responder about how to provide proper treatment to a patient.\n\nThe Association of Public Safety Communications Officials (APCO) International is an established industry organization of public safety communications professionals from a variety of public safety disciplines, including law enforcement, fire service, and EMS [32]. APCO International assists public safety practitioners by providing professional development, technical assistance, advocacy, training, and outreach services. The organization also runs an online application community known as AppComm-a central repository of mobile apps dedicated to public safety and its use cases [34].\n\nA law enforcement officer needs to identify an individual in a remote area. They use a wearable sensor to capture biometrics to facilitate the identification of the user. The information is transmitted to HQ for processing. The officer receives the results, which provide improved situational awareness and enable an informed action. Depending on coverage, the device may operate in limited offline mode, over 802.11 wireless, LTE, or satellite communications."}], "metadata": {"source": "Security Analysis of First Responder Mobile and Wearable 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 does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance:\n\n## Revision to Include Updates in Cybersecurity Framework Version 1.1\n\nThe Cybersecurity Framework Manufacturing Profile, NISTIR 8183, is scheduled to be revised to include the updates in the Cybersecurity Framework Version 1.1, and will be published as NISTIR 8183, Revision 1.\n\nOnce NISTIR, 8183, Revision 1 has been released, this implementation guide will be revised to include the updates in the Cybersecurity Framework Version 1.1 as well, and will be published as NISTIR 8183A, Revision 1."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 1 – General Implementation Guidance", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AT.L2-3.2.2 (NIST 3.2.2)?"}, {"role": "assistant", "content": "According to Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach:\n\n3.2.2 Develop the Cyber Resiliency Baseline ... 3.2.2. 3.2.2 Develop the Cyber Resiliency Baseline\n\nIn order to determine whether cyber resiliency improvement is needed, the baseline for the\nsystem (as it is understood at the stage in the life cycle when the cyber resiliency analysis is\nperformed) must be established."}], "metadata": {"source": "Developing Cyber-Resilient Systems_ A Systems Security Engineering Approach", "cmmc_level": "all", "nist_control": "3.2.2", "cmmc_practice_id": "AT.L2-3.2.2", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations:\n\nTLS is a protocol created to provide authentication, confidentiality, and data integrity protection between two communicating applications. TLS is based on a precursor protocol called the Secure Sockets Layer Version 3.0 (SSL 3.0) and is considered to be an improvement to SSL 3.0. SSL 3.0 is specified in [32]. The Transport Layer Security version 1 (TLS 1.0) is specified in Request for Comments (RFC) 2246 [23]. Each document specifies a similar protocol that provides security services over the Internet. TLS 1.0 has been revised to version 1.1, as documented in RFC 4346 [24], and TLS 1.1 has been further revised to version 1.2, as documented in RFC 5246 [25]. In addition, some extensions have been defined to mitigate some of the known security vulnerabilities in implementations using TLS versions 1.0, 1.1, and 1.2. TLS 1.3, described in RFC 8446 [57], is a significant update to previous versions that includes protections against security concerns that arose in previous versions of TLS. - More consistent use of authentication, confidentiality, and integrity mechanisms for the protection of information transported across the Internet;\n- Consistent use of the recommended cipher suites that encompass NIST-approved algorithms and open standards;\n- Protection against known and anticipated attacks on the TLS protocol; and\n\n| Executive Summary..................................................................................................... | Executive Summary..................................................................................................... | Executive Summary....................................................................................................."}], "metadata": {"source": "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium:\n\n22[12]) -  NIST Framework for Improving Critical Infrastructure Cybersecurity [2] -  NIST IR 8023, Risk Management for Replication Devices [13] -  NIST SP 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations [1] -  NIST SP 800-82, Revision 2, Guide to Industrial Control Systems (ICS) Security [14] - [1] NIST Special Publication (SP) 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations , Gaithersburg, Maryland, 2013, http://dx.doi.org/10.6028/NIST.SP.800-53r4 - [2] Cybersecurity Framework, National Institute of Standards and Technology, http://www.nist.gov/cyberframework/, 2014 - [3] ISO / ASTM52915 - 13, Standard Specification for Additive Manufacturing File Format (AMF) Version 1.1 , Astm, 2013, http://www.astm.org/Standards/ISOASTM52915.htm - [4] IEC 62264-1:2013, Enterprise-control system integration -- Part 1: Models and terminology , International Organization for Standardization, 2013, http://www.iso.org/iso/catalogue\\_detail.htm?csnumber=57308 - [5] ISA-95, Enterprise-Control System Integration , International Society of Automation, https://www.isa.org/isa95/ - [6] ISO 10303-242:2014, Industrial automation systems and integration -- Product data representation and exchange -- Part 242: Application protocol: Managed model-based 3D engineering , International Organization for Standardization, 2014, http://www.iso.org/iso/iso\\_catalogue/catalogue\\_tc/catalogue\\_detail.htm?csnumber=5762 0 - [7] ISO 14306:2012, Industrial automation systems and integration -- JT file format specification for 3D visualization , International Organization for Standardization,2012, http://www.iso.org/iso/catalogue\\_detail.htm?csnumber=60572 -"}], "metadata": {"source": "Proceedings of the Cybersecurity for Direct Digital Manufacturing (DDM) Symposium", "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 IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog:\n\n| 62 | |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------| | (CSC) Cybersecurity Capabilities..................................................................62 | | | (EOL) End-of-Life (Reprovisioning and Disposal) .........................................64 | | | (RSP) Cybersecurity Responsibilities............................................................64 | | | (EXP) Cybersecurity Expectations and Assumptions....................................65 | | | (BAK) Data Back-up......................................................................................66 | | | (VMG) Vulnerability Management Options....................................................67 | | | References...................................................................................................................69 | | | List of Appendices | List of Appendices | | Definition of the Federal Profile for IoT Device Cybersecurity Requirements ..............................................................................................................71 | | | Mapping of SP 800-53 Controls to Device Cybersecurity Requirements ..............................................................................................................75 | | | Mapping of Cybersecurity Framework Outcomes to Device Cybersecurity Requirements .....................................................................................83 | | | Acronyms............................................................................................91 Glossary...............................................................................................92 | |"}], "metadata": {"source": "IoT Device Cybersecurity Guidance for the Federal Government_ IoT Device Cybersecurity Requirement Catalog", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Profile for Liquefied Natural Gas:\n\n| Category........................................................................................................................................23 |\n| Table 22.\nCSF Subcategory Priorities for the Identify Function's Business Environment (ID.BE) Category........................................................................................................................................23 | |\n| Table 23. CSF Subcategory Priorities for the Identify Function's Governance (ID.GV) Category. .......................................................................................................................................................24 | |\n| Table 24. CSF Subcategory Priorities for the Identify Function's Risk Assessment (ID.RA) Category........................................................................................................................................24 | |\n| Table 25. CSF Subcategory Priorities for the Identify Function's Risk Management Strategy (ID.RM) | Category..........................................................................................................................25 |\n| Table 26. CSF Subcategory Priorities for the Identify Function's Supply Chain Management (ID.SC) Category."}], "metadata": {"source": "Cybersecurity Framework Profile for Liquefied Natural Gas", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Guide for Developing Security Plans for Federal Information Systems:\n\nification of compensating controls; and (iii) the specification of agency-defined parameters in the security controls, where allowed. The system security plan should document all tailoring activities.\n- -Security controls that uniquely support the confidentiality, integrity, or availability security objectives can be downgraded to the corresponding control in a lower baseline (or appropriately modified or eliminated if not defined in a lower baseline) if, and only if, the downgrading action: (i) is consistent with the FIPS 199 security categorization for the corresponding security objectives of confidentiality, integrity, or availability before moving to the high watermark; 14 (ii) is supported by an agency's assessment of risk; and (iii) does not affect the security-relevant information within the information system. 15"}], "metadata": {"source": "Guide for Developing Security Plans for Federal Information Systems", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to NIST Cloud Computing Forensic Science Challenges:\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": "NIST Cloud Computing Forensic Science Challenges", "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.1 (NIST 3.2.1)?"}, {"role": "assistant", "content": "According to PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance):\n\n3.2.1 PIV Card Application Card Command Interface Tests ... 3.2.1 PIV Card Application Card Command Interface Tests ... 3.2.1 PIV Card Application Card Command Interface Tests ..."}], "metadata": {"source": "PIV Card Application and Middleware Interface Test Guidelines (SP 800-73-4 Compliance)", "cmmc_level": "all", "nist_control": "3.2.1", "cmmc_practice_id": "AT.L2-3.2.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Guide for Conducting Risk Assessments:\n\nnimum organization-wide security controls; (vi) conformance to enterprise/security architectures; and (vii) monitoring strategies and ongoing authorizations of information systems and common controls.\nAt Tier 2, risk assessments can affect, for example: (i) enterprise architecture/security architecture design decisions; (ii) the selection of common controls; (iii) the selection of suppliers, services, and contractors to support organizational missions/business functions; (iv) the development of risk-aware mission/business processes; and (v) the interpretation of information security policies with respect to organizational information systems and environments in which those systems operate. Finally, at Tier 3, risk assessments can affect, for example: (i) design decisions (including the selection, tailoring, and supplementation of security controls and the selection of information technology products for organizational information systems); (ii) implementation decisions (including whether specific information technology products or product configurations meet security control requirements); and (iii) operational decisions (including the requisite level of monitoring activity, the frequency of ongoing information system authorizations, and system maintenance decisions)."}], "metadata": {"source": "Guide for Conducting Risk Assessments", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Risk Management for Replication Devices provide? (Part 5)"}, {"role": "assistant", "content": "...............................................11 |\n| Appendix A - References..........................................................................................................................\nA-1 |\n| Appendix B - Sample Security Risk Assessment....................................................................................B-1 |\n| Security Risk Assessment Table for Replication Devices (RDs) .............................................................B-2 |\n| Security Risk Assessment Flow Chart for Replication Devices (RDs)....................................................B-7 |\n| Total Risk Scores and Risk Levels ........................................................................................................B-11 |\n| Appendix C: Roles and Responsibilities ................................................................................................. C-1 |\n\n## 1. Introduction\n\nA replication device (RD) is any device that reproduces (e.g., copies, prints, scans) documents, images, or objects from an electronic or physical source. For the purposes of this NISTIR, RDs include copiers, printers, three-dimensional (3D) printers, scanners, 3D scanners, as well as multifunction machines when used as a copier, printer, or scanner. RDs in use within organizations run the gamut in terms of age and functionality. Older, single-function devices may have no internal, nonvolatile storage and cannot be networked. Other devices may provide a variety of functions, be network-connected, run commercially available operating systems, contain internal, nonvolatile storage, and contain embedded internal print servers and web server capability. In between the two extremes, there may be RDs with network and/or storage functionality but no discernable means to configure them securely."}], "metadata": {"source": "Risk Management for Replication Devices", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by Federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, Federal agencies may wish to closely follow the development of these new publications by NIST.\n\n-  Lack of Physical Security Controls. Telework client devices are used in a variety of locations outside the organization's control, such as users' homes, coffee shops, hotels, and conferences. The mobile nature of these devices makes them more likely to be lost or stolen, which places the data on the devices at increased risk of compromise. When planning telework security policies and controls, organizations should assume that client devices will be acquired by malicious parties who will either attempt to recover sensitive data from the devices or leverage the devices to gain access to the enterprise network.\n\nAdditional information on the four categories of remote access methods is provided below. When planning a remote access solution, organizations should carefully consider the security implications of the remote access methods in each category, in addition to how well each method may meet operational requirements."}], "metadata": {"source": "Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) 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 does CMMC require for Media Protection?"}, {"role": "assistant", "content": "According to Guide for Security-Focused Configuration Management of Information Systems:\n\n| senior information security officer | See Senior Agency Information Security Officer. |\n|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| spyware [CNSSI-4009] | Software that is secretly or surreptitiously installed into an information system to gather information on individuals or organizations without their knowledge; a type of malicious code. |\n| system [CNSSI 4009] | Any organized assembly of resources and procedures united and regulated by interaction or interdependence to accomplish a set of specific functions. Note: Systems also include specialized systems such as industrial/process controls systems, telephone switching and private branch exchange (PBX) systems, and environmental control systems. |\n| system administrator [SP 800-37] | An individual, group, or organization responsible for setting up and maintaining a system or specific system elements, implements approved secure baseline configurations, incorporates secure configuration settings for IT products, and conducts/assists with configuration monitoring activities as needed. |\n| system component | A discrete identifiable information technology asset that represents a building block of a system and may include hardware, software, and firmware. |\n| system owner (or program manager) [SP 800-37] | An organizational official responsible for the procurement, development, integration, modification, operation, maintenance, and disposal of a system."}], "metadata": {"source": "Guide for Security-Focused Configuration Management of Information Systems", "cmmc_level": "all", "cmmc_domain": "Media Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AC.L2-3.1.3 (NIST 3.1.3)?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\n\n3.1.3). 3.1.3 Arm Realm Memory Isolation and Protection\n\nAs shown in Figure 11, TrustZone provides two security states each associated with its own PAS: the Secure PAS and the Non-secure PAS."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "nist_control": "3.1.3", "cmmc_practice_id": "AC.L2-3.1.3", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Program Review for Information Security Management Assistance (PRISMA):\n\nIntroduction .........................................................................................................................1 | |----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| | | 1.1 | Purpose.......................................................................................................................1 | | | | 1.2 | Legislative Background...............................................................................................2 | | | | 1.3 | PRISMA......................................................................................................................2 | | | | 1.4 | PRISMA Assumptions and Constraints ......................................................................3 | | | | 1.5 | Audience.....................................................................................................................4 | | | | 1.6 | Document Organization | ..............................................................................................4 | | 2."}], "metadata": {"source": "Program Review for Information Security Management Assistance (PRISMA)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Security and Trust Considerations for Digital Twin Technology:\n\noperators to form models and visual representations of oil rigs, drill rigs, and drill bit heads deep in the ocean. - Robotic surgery: There are surgical robots that perform various kinds of surgery.\nSome require an actual human surgeon to control the robot, while others only require a human surgeon to monitor the robot's automatic execution of the surgery. Digital twin technology could be used in pre-surgery planning and to foster surgical tool interoperability. For example, one company's surgical robot could interoperate with another company's VR system that specializes in the representation of human organs."}], "metadata": {"source": "Security and Trust Considerations for Digital Twin Technology", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 1 require for Physical Protection?"}, {"role": "assistant", "content": "According to A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data:\n\nzation is a key technology in cloud computing environments that enables ubiquitous access to shared pools of system resources and high-level services provisioned with minimal management effort [1, 2].\nAn Operating System (OS) directly controls hardware resources in a non-virtualized system, but virtualization, typically performed by a hypervisor (also called a virtual machine monitor or VMM) [3] within a cloud environment, provides a mechanism that abstracts the hardware and system resources from an OS. As a software layer that lies between the physical hardware and the Virtual Machines (VMs or guest machines), a hypervisor supports the guest machines by presenting the guest OSs with a virtual operating platform and managing their execution."}], "metadata": {"source": "A Methodology for Enabling Forensic Analysis Using Hypervisor Vulnerabilities Data", "cmmc_level": "1", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.:\n\n| Company Overview.................................................................................................................2 |\n|--------------------------------------------------------------------------------------------------------------------------------------------|\n| Risk Profile ..........................................................................................................................2 |\n| Highlighted Practices in Cyber Supply Chain Management ..................................................2 |\n| Organizational Approach to Supply Chain Risk and Cybersecurity............................................3 |\n| Supplier Management.............................................................................................................4 |\n| Key Aspects of Managing Supplier Relationships .................................................................4 |\n| Measuring Supplier Risk ......................................................................................................5 |\n| Quality Management and Continuous Improvement...........................................................5 |\n| Incident Response and Recovery .........................................................................................6 |\n| Lessons Learned and Improvement Opportunities ..................................................................7 |\n| References ..............................................................................................................................8 |\n\n## Incident Response and Recovery\n\nConfirmed incidents trigger the formal incident response plan (IRP)."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Computer Security Division 2008 Annual Report:\n\n| Computer Security Division Publications - FY 2008 | 53 55 | | Ways to Engage Our Division and NIST | | | Acknowledgements | 56 |"}], "metadata": {"source": "Computer Security Division 2008 Annual Report", "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 IR.L2-3.6.1 (NIST 3.6.1)?"}, {"role": "assistant", "content": "According to Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio:\n\n3.6.1. 3.6.1."}], "metadata": {"source": "Enterprise Impact of Information and Communications Technology Risk_ Governing and Managing ICT Risk Programs Within an Enterprise Risk Portfolio", "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 Level 3 require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Security Requirements for Cryptographic Modules:\n\nCATEGORY: INFORMATION SECURITY SUBCATEGORY: CRYPTOGRAPHY\n\nKey words : computer security; telecommunication security; physical security; software security; cryptography; cryptographic modules; Federal Information Processing Standard (FIPS); ISO/IEC 19790; ISO/IEC 24759.\n\n1. Name of Standard. Security Requirements for Cryptographic Modules (FIPS PUB 140-3).\n2. Category of Standard. Computer Security Standard, Cryptography.\n3. Explanation. This standard specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system protecting sensitive but unclassified information (hereafter referred to as sensitive information). The standard provides four increasing, qualitative levels of security: Level 1, Level 2, Level 3, and Level 4. These levels are intended to cover the wide range of potential applications and environments in which cryptographic modules may be employed. The security requirements cover areas related to the secure design and implementation of a cryptographic module. These areas include cryptographic module specification; cryptographic module interfaces; roles, services, and authentication; software/firmware security; operating environment; physical security; non-invasive security; sensitive security parameter management; self-tests; life-cycle assurance; and mitigation of other attacks. This standard supersedes FIPS 140-2, Security Requirements for Cryptographic Modules , in its entirety."}], "metadata": {"source": "Security Requirements for Cryptographic Modules", "cmmc_level": "3", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture:\n\nntific data formatting library with only seven dependencies, while Data Mining Classification and Regression Methods (rminer) [21] - an R-based data mining application - has 150 software dependencies.\nThe full software stack can be split into three general categories that differ based on the maintainer: user software, facility software, and vendor software."}], "metadata": {"source": "High-Performance Computing Security_ Architecture, Threat Analysis, and Security Posture", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to 2019 NIST_ITL Cybersecurity Program Annual Report:\n\nThe NCCoE launched a project to demonstrate an approach for improving enterprise patching practices for general IT systems. In this project, commercial and open-source tools will be used to address the most challenging aspects of patching, including system characterization and prioritization, patch testing, and patch implementation tracking and verification. These tools are accompanied by actionable, prescriptive guidance on establishing policies and processes for the entire patching life cycle. For example, roles and responsibilities are defined for all affected personnel, and a playbook is established with rapid mitigation actions for destructive malware outbreaks that organizations can tactically execute in the first 30 days as well as recommendations that can be implemented strategically beyond 30 days. This project has resulted in\n\n- Guest Research Internships opportunities at ITL for 6- to 24-month terms. Qualified individuals should contact ITL (itl\\_inquiries@nist.gov) to provide qualifications and indicate the area of work that is of interest. - The NIST Pathways Program offers paths to federal internships for students from high school through post-graduate school as well as careers for recent graduates. It provides training and career development opportunities for individuals who are at the beginning of their federal service. For further details on Pathways and other student programs at NIST, please see https:/ /www.nist.gov/ohrm/staffing/ students.cfm. - The ITL Summer Undergraduate Research Fellowship (SURF) Program is designed to provide hands-on research experience in applied mathematics, statistics, computer security, information access, software testing, and networking technologies. See https:/ /www.nist.gov/itl/how-work-us/itl-surf-program. - Opportunities for a temporary assignment of government or military personnel for 6- to 24-month details in ITL."}], "metadata": {"source": "2019 NIST_ITL Cybersecurity Program Annual Report", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to PBX Administrator’s Security Standards:\n\nons | A-1 |\n\n- Become knowledgeable about PBX and all adjurKt system capabilities. - Monitor all PBX and adjunct system options and settings periodically.\n- Set all passwords to conform to FDIC requirements. - Ensure that telephone bills and call detail reports are reviewed for fraud and abuse. - Educate fellow employees about how to avoid PBX fraud. - Determine appropriate time of day/day of week access restrictions. - Shred and dispose of old PBX manuals. - Protect corporate telephone books and directories from unauthorized access. - Know the symptoms of PBX and voice mail fraud. - Protect your voice mail system from unauthorized access. - Restrict DID and outward calling access to stations with an operational requirement. - Prohibit the use of Direct Inward System Access (DISA). - Restrict call transfer capability to within the PBX for automated attendant systems. - Enforce monthly change of PBX and adjunct system administration passwords. - Block country code access where FDIC operations do not take place. - Limit telephone service to that required by the station. - Protect modem pools by using COS/COR restrictions. - Restrict direct access to trunks and trunk groups. - Restrict the ability of incoming calls to access outgoing trunks. - Use FDIC's networking services to maximize calling efficiertcy and to minimize abuse. - Ensure that PBX, adjunct system equipment, and wire closets are physically secure. - Apply physical security measures to shared building or telephone facilities. - Apply PBX security measures to key telephone systems, to the extent possible. - Maintain up-to-date, complete configuration management records. - Maintain copies of all contractual agreements for PBXs and PBX services. - Ensure that end users are aware of their telephone system security responsibilities. - Report all PBX related security incidents to the VNSU and ASU."}], "metadata": {"source": "PBX Administrator’s Security Standards", "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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Service Mesh Proxy Models for Cloud-Native Applications:\n\n| October 2024 | October 2024 | Cloud-Native Applications |\n|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|\n| 5.2.7. | Denial of Service (TR-7)...........................................................................................................19 | |\n| 5.2.8."}], "metadata": {"source": "Service Mesh Proxy Models for Cloud-Native Applications", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Security Property Verification by Transition Model:\n\nThere may be references in this publication to other publications currently under development by NIST in accordance with its assigned statutory responsibilities. The information in this publication, including concepts and methodologies, may be used by federal agencies even before the completion of such companion publications. Thus, until each publication is completed, current requirements, guidelines, and procedures, where they exist, remain operative. For planning and transition purposes, federal agencies may wish to closely follow the development of these new publications by NIST.\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems."}], "metadata": {"source": "Security Property Verification by Transition Model", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Guide to Integrating Forensic Techniques into Incident Response:\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 nationGLYPH<146>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. ITLGLYPH<146>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 ITLGLYPH<146>s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations.\n\nThis section discusses several aspects of organizing a forensics capability for an organization. It begins by showing the wide variety of potential uses for forensics, and then presents a high-level overview of the forensics process. The next part of the section discusses how forensics services are typically provided and provides guidance on building and maintaining the necessary skills to perform forensics tasks. The section also explains the need to include various teams from throughout the organization, such as legal advisors and physical security staff, in some forensic activities. The section ends by discussing how policies, guidelines, and procedures should address forensics (e.g., defining roles and responsibilities, providing guidance on the proper usage of tools and techniques, incorporating forensics into the information system life cycle).\n\n- ! Operational Troubleshooting. Many forensic tools and techniques can be applied to troubleshooting operational issues, such as finding the virtual and physical location of a host with"}], "metadata": {"source": "Guide to Integrating Forensic Techniques into Incident Response", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to 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 does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Cybersecurity of Genomic Data:\n\n| Potential Privacy Problems........................................................................................9 | |\n| 3.3. | Discrimination and Reputational Concerns..............................................................10 | |\n| 3.4. | Economic Concerns.................................................................................................11 | |\n| 3.5. | Health Outcome Concerns ......................................................................................11 | |\n| 3.6. | Other Potential Future Concerns.............................................................................11 | |\n| 3.7."}], "metadata": {"source": "Cybersecurity of Genomic Data", "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 2020 Cybersecurity and Privacy Annual Report provide? (Part 3)"}, {"role": "assistant", "content": "in the role of the Red Queen in Lewis Carroll's 'Through the Looking-Glass.' In that classic, the Queen tells Alice: \"Now, here, you see, it takes all the running you can do to keep in the same place.\nIf you want to get somewhere else, you must run at least twice as fast as that!\"\n\nIt is true that leaders need to be nimble and move quickly to avoid the consequences of cybersecurity and privacy attacks that threaten their enterprises. That need extends to government agencies, like NIST, that are trying to help meet those urgent challenges. At NIST, we know that - in addition to current needs - we also have a responsibility to keep an eye on the horizon, anticipating technology changes, threat environments, and cultural shifts that could affect the ability of organizations to manage cybersecurity and privacy risks. We've successfully carried out our work for nearly 50 years precisely because we not only address near-term challenges but also spend time thinking, exploring, listening, and speaking with others about the really big issues in store for all of us. We tackle current issues, but we also play the long game - the infinite game, if you will. We are mindful of the reality that cybersecurity and privacy challenges are evolving. At NIST, we make it our business to help others be prepared by anticipating needs and creating opportunities. We anchor our decisions with our feet firmly planted in both the present and the future. As you read this report about our efforts and accomplishments in 2020, you will understand how we have been addressing both short-term and long-term needs."}], "metadata": {"source": "2020 Cybersecurity and Privacy Annual Report", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.4 (NIST 3.5.4)?"}, {"role": "assistant", "content": "According to Contingency Planning Guide for Federal Information Systems:\n\n3.5.4 TT&E | Exercises... 3.5.4 provides guidance on the type of TT&E identified for each FIPS 199 impact level. 3.5.4 TT&E Program Summary\n\nA TT&E program provides an overall framework for determining, scheduling, and setting objectives for TT&E activities."}], "metadata": {"source": "Contingency Planning Guide for Federal Information Systems", "cmmc_level": "all", "nist_control": "3.5.4", "cmmc_practice_id": "IA.L2-3.5.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security Considerations for Voice Over IP Systems:\n\n- difficulties, particularly in key management. Here, access control mechanisms and policy enforcement may help. - ƒ A mechanism to allow VOIP traffic through firewalls is required. There are a variety of protocol dependent and independent solutions, including application level gateways (ALGs) for VOIP protocols, Session Border Controllers, or other standards-based solutions when they mature. - ƒ Stateful packet filters can track the state of connections, denying packets that are not part of a properly originated call. (This may not be practical when multimedia protocol inherent security or lower layer security is applied, e.g., H.235 Annex D for integrity provision or TLS to protect SIP signaling.)\n- ƒ Use IPsec or Secure Shell (SSH) for all remote management and auditing access. If practical, avoid using remote management at all and do IP PBX access from a physically secure system. - If performance is a problem, use encryption at the router or other gateway, not the individual endpoints, to provide for IPsec tunneling. Since some VOIP endpoints are not computationally powerful enough to perform encryption, placing this burden at a central point ensures all VOIP traffic emanating from the enterprise network has been encrypted. Newer IP phones are able to provide Advanced Encryption System (AES) encryption at reasonable cost. Note that Federal Information Processing Standard (FIPS) 140-2, Security Requirements for Cryptographic Modules, is applicable to all Federal agencies that use cryptographic-based security systems to protect sensitive information in computer and telecommunication systems (including voice systems) as defined in Section 5131 of the Information Technology Management Reform Act of 1996, Public Law 104-106. 2. Ensure that the organization has examined and can acceptably manage and mitigate the risks to their information, system operations, and continuity of essential operations when deploying VOIP systems."}], "metadata": {"source": "Security Considerations for Voice Over IP Systems", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guide to Secure Web Services:\n\n| Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | Executive Summary..............................................................................................................ES-1 | |---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | Introduction | | ......................................................................................................................1-1 | | | 1.1 | Authority...................................................................................................................1-1 | Authority...................................................................................................................1-1 | | | 1.2 | Purpose and Scope .................................................................................................1-1 | Purpose and Scope .................................................................................................1-1 | | | 1.3 | Audience..................................................................................................................1-1 | Audience..................................................................................................................1-1 | | | 1.4 | Document Structure.................................................................................................1-2 | Document Structure.................................................................................................1-2 | | | 2."}], "metadata": {"source": "Guide to Secure Web Services", "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 are the CMMC Level 1 requirements?"}, {"role": "assistant", "content": "According to Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop:\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\nThis report provides a summary of the discussion and findings from the NIST Cybersecurity Risks in Consumer Home Internet of Things (IoT) Devices virtual workshop in October 2020."}], "metadata": {"source": "Workshop Summary Report for “Cybersecurity Risks in Consumer Home Internet of Things (IoT) Products” Virtual Workshop", "cmmc_level": "1", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "cmmc_requirement"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What guidance does PBX Administrator’s Security Standards provide?"}, {"role": "assistant", "content": "I\n\n\n\nI\n\n## PBX Administrator's Security Standards\n\n## Deveioped by the Federai Deposit insurance Corporation\n\nNISTIR 4816\n\n## Edward Roback NIST Coordinator\n\nU.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899\n\n\n\n## PBX Administrator's Security Standards\n\n## Deveioped by the Federai Deposit insurance Corporsition\n\n## Edward Roback NIST Coordinator\n\nU.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Gaithersburg, MD 20899\n\nApril 1992\n\n\n\nU.S. DEPARTMENT OF COMMERCE Barbara Hackman Franklin, Secretary\n\nTECHNOLOGY ADMINISTRATION Robert M. White, Under Secretary for Technology\n\nNATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY John W. Lyons, Director\n\n•%)<'<5tWtaR's'f\n\n'M\n\n^c. ^.^i4i<^^'l w J'f'fi'\n\nriV»lT^S5^\n\n^0\n\n## Preface\n\nThis National Institute of Standards and Technology Interagency Report (NISTIR) presents the Federal Deposit Insurance Corporation's (FDIC) PBX Administrator's Security Standards . It was developed to provide a generic set of security standards to phone system administrators and users throughout FDIC. The document discusses telephone policy, PBX fraud, PBX administration and anticipated future concerns. The duties and responsibilities for PBX system administrators may prove to be of particular interest to federal departments and agencies. The National Institute of Standards and Technology (NIST) makes no claim or endorsement of these standards. However, as this material may be of use to other organizations, it is being reprinted by NIST to provide for broad public dissemination of this federally sponsored work. This publication is part of a continuing effort to assist federal agencies in accordance with NIST's mandate under the Computer Security Act of 1987. NIST expresses its appreciation to FDIC for their kind permission to publish this report."}], "metadata": {"source": "PBX Administrator’s Security Standards", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 0}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Awareness and Training?"}, {"role": "assistant", "content": "According to Security Architecture Design Process for Health Information Exchanges (HIEs):\n\nining, human resources issues, or nontechnical privacy issues, it does describe an architecture design process that allows for their integration into the information technology architecture of an HIE.\n| Capstone Policy Drivers | Entities Affected | Enabling Services Affected | Comment |\n|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Federal Regulations: Electronic Records; Electronic Signatures; Electronic Submissions; Establishment of Public Docket; Notice 28 CFR Part 11 | Research facilities that transmit information to the Food and Drug Administration | Entity Identity Assertion (Authentication)."}], "metadata": {"source": "Security Architecture Design Process for Health Information Exchanges (HIEs)", "cmmc_level": "all", "cmmc_domain": "Awareness and Training", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Guidelines for Smart Grid Cybersecurity provide? (Part 5)"}, {"role": "assistant", "content": "...................................................... 4\n1.2 Scope and Definitions ....................................................................................................................\n5\n1.3 Smart Grid Cybersecurity Document Development Strategy ........................................................ 6\n1.4 Combined Cyber-Physical Attacks .............................................................................................. 12\n CHAPTER 2 LOGICAL ARCHITECTURE AND INTERFACES OF THE SMART GRID ......................14\n2.1 The Seven Domains to the Logical Reference Model ................................................................. 15\n2.2 Logical Security Architecture Overview ..................................................................................... 24\n2.3 Logical Interface Categories ........................................................................................................ 28\n CHAPTER 3 HIGH-LEVEL SECURITY REQUIREMENTS ...............................................................75\n3.1 Cybersecurity Objectives ............................................................................................................. 75\n3.2 Confidentiality, Integrity, and Availability Impact Levels .......................................................... 76\nImpact Levels for the CI&A Categories ...................................................................................... 77\n3.3\n3.4 Selection of Security Requirements ............................................................................................. 79\n3.5 Security Requirements Example .................................................................................................. 80\n3.6 Recommended Security Requirements ........................................................................................ 81\n3.7 Access Control (SG.AC) ............................................................................................................."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.:\n\nSecurity and data protection are inseparable from Palo Alto Networks' role as a cybersecurity product provider. Thousands of companies and governments around the world rely on these products to protect highly sensitive information. For Palo Alto Networks, cybersecurity and product integrity are an implicit corporate mandate. Given Palo Alto Networks' role as a cybersecurity vendor, the company is subject to intense scrutiny from potential customers and is a target for a variety of threat actors. Recognizing that a product security incident could have an enormous impact on customers, Palo Alto Networks considers cybersecurity and product integrity an implicit corporate mandate. All products are subject to the company's end-to-end product security framework (E2E Framework). The framework is designed to provide defense in depth for each stage of the product lifecycledesign, sourcing, manufacturing, fulfilment, and service. Each stage is independently evaluated to determine security risks, and domain experts select relevant public standards and best practices to target those risks. Selected standards include the Federal Information Processing Standards (FIPS) i , Common Criteria ii , and the United Kingdom's Commercial Product Assurance (CPA) iii . Palo Alto Networks provides functional testing infrastructure for all products to the CM. These platforms are designed in-house and perform software diagnostics to ensure product integrity. While the tests are performed by the CM, the testing infrastructure remains under Palo Alto Networks' control. Tested products are outfitted with tamper-evident packaging and shipping labels featuring unique product identifiers, such as part and serial numbers, to ensure that the products received by the customer were not compromised in transit."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "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 Minimum Security Requirements for Federal Information and Information Systems provide? (Part 5)"}, {"role": "assistant", "content": "extended to reflect: (i) the experience gained from using the controls; (ii) the changing security requirements within federal agencies; and (iii) the new security technologies that may be available.\nThe minimum security controls defined in the low, moderate, and high security control baselines are also expected to change over time as well, as the level of security and due diligence for mitigating risks within federal agencies increases. The proposed additions, deletions, or modifications to the catalog of security controls and the proposed changes to the security control baselines in NIST Special Publication 800-53 will go through a rigorous, public review process to obtain government and private sector feedback and to build consensus for the changes. Federal agencies will have up to one year from the date of final publication to fully comply with the changes but are encouraged to initiate compliance activities immediately. ## 11. Waivers. No provision is provided under FISMA for waivers to FIPS made mandatory by the Secretary of Commerce. ## 12. Where to Obtain Copies. This publication is available from the NIST Computer Security Division web site by accessing http://csrc.nist.gov/publications."}], "metadata": {"source": "Minimum Security Requirements for Federal Information and Information Systems", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guide to a Secure Enterprise Network Landscape:\n\ntection and response (EDR) solutions that collect security telemetry data on endpoints. Any threat that is already inside of a network can move laterally and remain undetected for days or even months.\n- Edge computing [1], where much of the computing takes place close to the location of multiple IoT devices that may be geographically dispersed\n- Users located both within and outside of the corporate network, such as in homes, remote branch offices, and public locations (e.g., hotels, pubs); some enterprises must also provide access to ecosystem partners, who may be on their own corporate networks"}], "metadata": {"source": "Guide to a Secure Enterprise Network Landscape", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\n- Roles, Responsibilities, and Authorities (GV.RR): Cybersecurity roles, responsibilities, and authorities to foster accountability, performance assessment, and continuous improvement are established and communicated - o GV.RR-01: Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving - o GV.RR-02: Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced - o GV.RR-03: Adequate resources are allocated commensurate with the cybersecurity risk strategy, roles, responsibilities, and policies - o GV.RR-04: Cybersecurity is included in human resources practices - Policy (GV.PO): Organizational cybersecurity policy is established, communicated, and enforced - o GV.PO-01: Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced - o GV.PO-02: Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission - Oversight (GV.OV): Results of organization-wide cybersecurity risk management activities and performance are used to inform, improve, and adjust the risk management strategy - o GV.OV-01: Cybersecurity risk management strategy outcomes are reviewed to inform and adjust strategy and direction - o GV.OV-02: The cybersecurity risk management strategy is reviewed and"}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "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 IR.L2-3.6.4 (NIST 3.6.4)?"}, {"role": "assistant", "content": "According to Module-Lattice-Based Digital Signature Standard:\n\n3.6.4 | No Floating-Point Arithmetic . 3.6.4 No Floating-Point Arithmetic\n\nImplementations of ML-DSA shall not use floating-point arithmetic, as rounding errors in floating point operations may lead to incorrect results in some cases."}], "metadata": {"source": "Module-Lattice-Based Digital Signature Standard", "cmmc_level": "all", "nist_control": "3.6.4", "cmmc_practice_id": "IR.L2-3.6.4", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Risk Management for Replication Devices:\n\n-  Unencrypted information: Unencrypted information is subject to unauthorized exposure and modification. Any information, including configuration data or passwords, sent unencrypted to a RD could be intercepted, exposed, and/or altered. -  Open ports/protocols: Open ports and protocols allow data to flow to and from a device. When unused ports/protocols are not disabled, attackers may be able to access a machine undetected. Repudiation issues (e.g., removing origination information from file metadata, deleting entries from usage logs), data tampering, exposure of management consoles, network bouncing (hiding the source of a user's network connection), information disclosure, or denial of service are some of the associated potential security incidents. -  Denial of service (DoS): RDs connected to the Internet may be more vulnerable to this threat which results in devices being temporarily unusable. -  Wireless connectivity: Wireless functionality allows communications via Bluetooth or 802.11 to other devices or with the Internet. As with wired RDs, if not encrypted, these communications may potentially be intercepted. -  Access permissions: Anyone with the necessary equipment and access can potentially compromise a RD. Some RDs allow remote access for automatic updates, configuration changes, or maintenance. If access is not controlled or automatic downloads verified, this capability could be used to install malware or rootkits, gain access to other areas of the network, compromise configuration settings including passwords, disable a device, or expose stored information."}], "metadata": {"source": "Risk Management for Replication Devices", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.3 (NIST 3.3.3)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation:\n\n3.3.3. 3.3.3."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 1 – PIV Card Application Namespace, Data Model and Representation", "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 Identification and Authentication?"}, {"role": "assistant", "content": "According to Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4):\n\n- (1) Data Integrity,\n- (2) Data Confidentiality,\n- (3) Data Origination Authentication, and\n- (4) Access Control.\n\n| Index | Service Element | Status | Support | Support |\n|-------------|------------------------------------------|----------|-----------|-----------|\n| TOSEO | Confidentiality | 0.1 | Y | N |\n| TOSEl | Connection Confidentiality | TOSEO:m | Y | N |\n| T0SE2 T0SE3 | Connectionless Confidentiality Integrity | - 0.1 | Y | N |\n| T0SE4 | Connection Integrity w Recovery | - | | |\n| T0SE5 | Connection Integrity wo Recovery | - | | |\n| T0SE6 | Connectionless Integrity | T0SE3:m | Y | N |\n| T0SE7 | Data Origination Authentication | m | Y | N |\n| T0SE8 | Access Control | o | Y | N |\n\n| Index | Service Element | Status | Support | Support |\n|---------|----------------------------------|-----------|-----------|-----------|\n| T3SE0 | Confidentiality | 0.1 | Y | N |\n| T3SE1 | Connection Confidentiality | T3SE0;m | Y | N |\n| T3SE2 | Connectionless Confidentiality | - | | |\n| T3SE3 | Integrity | 0.1 | Y | N |\n| T3SE4 | Connection Integrity w Recovery | - | | |\n| T3SE5 | Connection Integrity wo Recovery | T3SE3:o.2 | Y | N |\n| T3SE6 | Connectionless Integrity | T3SE3:o.2 | Y | N |\n| T3SE7 | Data Origination Authentication | m | Y | N |\n| T3SE8 | Access Control | 0 | Y | N |"}], "metadata": {"source": "Protocol Implementation Conformance Statement (PICS) Proforma for the SDNS Security Protocol at Layer 4 (SP4)", "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 Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures:\n\nMeasurement provides data that can enable an organization to examine the impacts of implementing information security programs, specific controls, and associated policies and procedures. Such data is integral when making risk-based decisions, weighing performance against designated metrics, and demonstrating compliance. Measurement can also increase accountability and strengthen governance by providing data that can facilitating the identification of the personnel responsible for controls implemented within specific organizational components or systems and support an environment that allows for continuous analysis and improvement."}], "metadata": {"source": "Measurement Guide for Information Security_ Volume 1 — Identifying and Selecting Measures", "cmmc_level": "all", "cmmc_domain": "Personnel Security", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI):\n\n## Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)\n\n## Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)\n\nThe purpose of this Special Publication is to provide appropriate and useful guidelines for assessing the reliability of issuers of Personal Identity Verification (PIV) Cards and Derived PIV Credentials. These issuers store personal information and issue credentials based on Office of Management and Budget (OMB) policies and on the standards published in response to Homeland Security Presidential Directive 12 (HSPD-12) and therefore are the primary target of the assessment and authorization under this guideline. The reliability of an issuer is of utmost importance when one organization (e.g., a federal agency) is required to trust the identity credentials of individuals that were created and issued by another federal agency. This trust will only exist if organizations relying on the credentials issued by a given organization have the necessary level of assurance that the reliability of the issuing organization has been established through a formal authorization process."}], "metadata": {"source": "Guidelines for the Authorization of Personal Identity Verification Card Issuers (PCI) and Derived PIV Credential Issuers (DPCI)", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Guidelines for Media Sanitization:\n\n| Executive Summary............................................................................................................................1 |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................2 |\n| 2. Background....................................................................................................................................5 |\n| 3. Summary of Sanitization Methods..................................................................................................8 |\n| 3.1.1. Clear Sanitization Method............................................................................................................8 |\n| 3.1.2. Purge Sanitization Method.........................................................................................................10 |\n| 3.1.3. Destroy Sanitization Method......................................................................................................11 |\n| 3.2.1. Strength of Cryptography for CE ................................................................................................12 |\n| 3.2.2. Applicability of CE.......................................................................................................................13 |\n| 3.2.3. Sanitization of Keys ....................................................................................................................13 |\n| 3.2.4. Quality of Cryptographic Implementations................................................................................15 |\n| 3.2.5."}], "metadata": {"source": "Guidelines for Media Sanitization", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Security and Privacy Controls for Information Systems and Organizations:\n\n............................................................. 16\n3.1 ACCESS CONTROL ..................................................................................................................\n18\n3.2 AWARENESS AND TRAINING ................................................................................................... 59\n3.3 AUDIT AND ACCOUNTABILITY ................................................................................................. 65\n3.4 ASSESSMENT, AUTHORIZATION, AND MONITORING ................................................................. 83\n3.5 CONFIGURATION MANAGEMENT ........................................................................................... 96\n3.6 CONTINGENCY PLANNING .................................................................................................... 115\n3.7 IDENTIFICATION AND AUTHENTICATION ............................................................................... 131\n3.8 INCIDENT RESPONSE ............................................................................................................ 149\n3.9 MAINTENANCE .................................................................................................................... 162\n3.10 MEDIA PROTECTION .......................................................................................................... 171\n3.11 PHYSICAL AND ENVIRONMENTAL PROTECTION .................................................................... 179\n3.12 PLANNING ........................................................................................................................ 194\n3.13 PROGRAM MANAGEMENT ................................................................................................. 203\n3.14 PERSONNEL SECURITY ........................................................................................................ 222\n3.15 PERSONALLY IDENTIFIABLE INFORMATION PROCESSING AND TRANSPARENCY ......................."}], "metadata": {"source": "Security and Privacy Controls for Information Systems and Organizations", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice IA.L2-3.5.2 (NIST 3.5.2)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case:\n\n3.5.2 Installation\n\n1. 3.5.2 Setup Instructions\n\n1. 3.5.2 Disabling of Unsecure services on Network Devices\n\nUse the following guidelines to disable unsecure services on all Allen Bradley devices of the Plant:\n\n1."}], "metadata": {"source": "Cybersecurity Framework Manufacturing Profile Low Impact Level Example Implementations Guide_ Volume 2 – Process-based Manufacturing System Use Case", "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 User's Guide to Telework and Bring Your Own Device (BYOD) Security provide? (Part 3)"}, {"role": "assistant", "content": "raft publications during public comment periods and provide feedback to NIST. Many NIST cybersecurity 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\nAll comments are subject to release under the Freedom of Information Act (FOIA). ## Reports on Computer Systems Technology\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national securityrelated information in federal information systems. The Special Publication 800-series reports on ITL's research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. ## Abstract\n\nMany people telework, and they use a variety of devices, such as desktop and laptop computers, smartphones, and tablets, to read and send email, access websites, review and edit documents, and perform many other tasks. Each telework device is controlled by the organization, a third party (such as the organization's contractors, business partners, and vendors), or the teleworker; the latter is known as bring your own device (BYOD)."}], "metadata": {"source": "User's Guide to Telework and Bring Your Own Device (BYOD) Security", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Conformance Assessment of Transport Layer Security Implementations:\n\needed for event reporting and auditing; and cryptography (i.e., employment of specific cryptographic algorithms) is needed to support Data Integrity, Data Confidentiality, and Authentication services.\nThese functions are normally collocated in an end-system, with an SP4 entity."}], "metadata": {"source": "Conformance Assessment of Transport Layer Security Implementations", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What is CMMC practice AU.L2-3.3.5 (NIST 3.3.5)?"}, {"role": "assistant", "content": "According to Cybersecurity Framework Version 1.1 Manufacturing Profile:\n\n3.3.5. 3.3.5."}], "metadata": {"source": "Cybersecurity Framework Version 1.1 Manufacturing Profile", "cmmc_level": "all", "nist_control": "3.3.5", "cmmc_practice_id": "AU.L2-3.3.5", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to The NIST Cybersecurity Framework (CSF) 2.0:\n\nurity incident are restored. RECOVER supports the timely restoration of normal operations to reduce the effects of cybersecurity incidents and enable appropriate communication during recovery efforts.\nWhile many cybersecurity risk management activities focus on preventing negative events from occurring, they may also support taking advantage of positive opportunities. Actions to reduce cybersecurity risk might benefit an organization in other ways, like increasing revenue (e.g., first offering excess facility space to a commercial hosting provider for hosting their own and other organizations' data centers, then moving a major financial system from the organization's in-house data center to the hosting provider to reduce cybersecurity risks)."}], "metadata": {"source": "The NIST Cybersecurity Framework (CSF) 2.0", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Recommendation for Key Management_ Part 1 – General:\n\n| 1 | | 1.1 | Purpose ..............................................................................................................................1 | Purpose ..............................................................................................................................1 | | | 1.2 | Audience............................................................................................................................1 | Audience............................................................................................................................1 | | | 1.3 | Scope .................................................................................................................................2 | Scope .................................................................................................................................2 | | | 1.4 | Purpose of FIPS and NIST Recommendations (NIST Standards) ....................................3 | Purpose of FIPS and NIST Recommendations (NIST Standards) ....................................3 | | | 1.5 | Content and Organization..................................................................................................4 | Content and Organization..................................................................................................4 | | | 2 Glossary of Terms and Acronyms..........................................................................."}], "metadata": {"source": "Recommendation for Key Management_ Part 1 – General", "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 Guidelines for Securing Wireless Local Area Networks (WLANs):\n\n1 | | | 1.1 | Authority....................................................................................................................1 | | | 1.2 | Purpose and Scope...................................................................................................1 | | | 1.3 | ...................................................................................................................1 | | | 1.4 | Audience Document Structure ..................................................................................................1 | | 2."}], "metadata": {"source": "Guidelines for Securing Wireless Local Area Networks (WLANs)", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Recommendation for Cryptographic Key Generation:\n\n11. New Section 6.3 (old Section 6.6) on combining multiple keys:\n- a. The notation for the other data items has been changed from Vi to Di to avoid a conflict with the use of Vi in Section 3.4.\n- b. Additional discussion on combining key components has been added.\n- c. Methods 2 and 3 from the previous version have been combined into the new Method 2.\n- d. A new method using HMAC has been added as (a new) Method 3.\n- e. Guidance for using each method has been further clarified.\n12. New Section 6.4: Moved from the old Section 6.2.\n13. References are now an independent section instead of an Appendix."}], "metadata": {"source": "Recommendation for Cryptographic Key Generation", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Planning?"}, {"role": "assistant", "content": "According to Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies:\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": "Report of the Virtual Workshop on Usable Cybersecurity and Privacy for Immersive Technologies", "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 AC.L2-3.1.1 (NIST 3.1.1)?"}, {"role": "assistant", "content": "According to Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface:\n\n3.1.1. 3.1.1."}], "metadata": {"source": "Interfaces for Personal Identity Verification_ Part 2 – PIV Card Application Card Command Interface", "cmmc_level": "all", "nist_control": "3.1.1", "cmmc_practice_id": "AC.L2-3.1.1", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products:\n\ninterfaces 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.\n| Vulnerability Factors | Example Relevant Tactics: Techniques from ATT&CK | Related Baseline Criteria |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| devices vulnerable to unauthorized access through internet and other network connections."}], "metadata": {"source": "Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Configuration Management?"}, {"role": "assistant", "content": "According to Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography:\n\nTo include bilateral key confirmation, two instances of unilateral key confirmation (as specified in Section 5.6.1, subject to the modifications listed below) shall be incorporated into the KAS2 scheme, once with party U as the key-confirmation provider (i.e., P = U and R = V) and once with party V as the key-confirmation provider (i.e., P = V and R = U). Additional details will be provided in Section 8.3.3.4."}], "metadata": {"source": "Recommendation for Pair-Wise Key-Establishment Using Integer Factorization Cryptography", "cmmc_level": "all", "cmmc_domain": "Configuration Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "How does The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1 support CMMC certification?"}, {"role": "assistant", "content": "According to The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1:\n\nr security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-126, Revision 1 39 pages (Feb.\n2011)\n\nCertain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. Such identification is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. ## Acknowledgments\n\nThe authors, David Waltermire and Stephen Quinn of the National Institute of Standards and Technology (NIST), and Karen Scarfone of G2, Inc., wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. The authors would like to acknowledge John Banghart, Harold Booth, Paul Cichonski, and Blair Heiserman of NIST; Christopher Johnson of HP Enterprise Services; Paul Bartock of the National Security Agency (NSA); Jeff Ito, Matt Kerr, Shane Shaffer, and Greg Witte of G2, Inc.; Andy Bove of SecureAcuity; Jim Ronayne of Varen Technologies; Adam Halbardier, Rhonda Farrell, Angela Orebaugh, and Victoria Thompson of Booz Allen Hamilton; Alan Peltzman of the Defense Information Systems Agency (DISA); and Jon Baker, Drew Buttner, Maria Casipe, and Charles Schmidt of the MITRE Corporation for their keen and insightful assistance throughout the development of the document. ## Trademark Information\n\nOVAL and CVE are registered trademarks, and CCE, CPE, and OCIL are trademarks, of The MITRE Corporation. XCCDF and SCAP are trademarks of NIST. Windows XP, Windows Vista, and Windows Server 2003 are registered trademarks of Microsoft Corporation. All other registered trademarks or trademarks belong to their respective organizations."}], "metadata": {"source": "The Technical Specification for the Security Content Automation Protocol (SCAP)_ SCAP Version 1.1", "cmmc_level": "2", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks:\n\nhe software implementation of the networking protocol that uses the card or chip). Examples of network interface capabilities include Ethernet, Wi-Fi, Bluetooth, Long-Term Evolution (LTE), and ZigBee.\nEvery IoT device has at least one enabled network interface capability and may have more than one. - Supporting capabilities provide functionality that supports the other IoT capabilities. Examples are device management, cybersecurity, and privacy capabilities. [2]"}], "metadata": {"source": "Considerations for Managing Internet of Things (IoT) Cybersecurity and Privacy Risks", "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 Guide to Protecting the Confidentiality of Personally Identifiable Information (PII):\n\nThe authors, Erika McCallister, Tim Grance, and Karen Scarfone of the National Institute of Standards and Technology (NIST), wish to thank their colleagues who reviewed drafts of this document and contributed to its technical content. Of particular note are the efforts of Joseph Nusbaum of Innovative Analytics & Training, Deanna DiCarlantonio of CUNA Mutual Group, and Michael L. Shapiro and Daniel I. Steinberg of Booz Allen Hamilton, who contributed significant portions to previous versions of the document. The authors would also like to acknowledge Ron Ross, Kelley Dempsey, and Arnold Johnson of NIST; Michael Gerdes, Beth Mallory, and Victoria Thompson of Booz Allen Hamilton; Brendan Van Alsenoy of ICRI, K.U.Leuven; David Plocher and John de Ferrari of the Government Accountability Office; Toby Levin of the Department of Homeland Security; Idris Adjerid of Carnegie Mellon University; The Federal Committee on Statistical Methodology: Confidentiality and Data Access Committee; The Privacy Best Practices Subcommittee of the Chief Information Officers Council; and Julie McEwen and Aaron Powell of The MITRE Corporation, for their keen and insightful assistance during the development of the document."}], "metadata": {"source": "Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.:\n\ns challenging for organizations at every maturity level. Palo Alto Networks leverages established contract manufacturers with demonstrably diligent cybersecurity and supplier risk management programs.\nGiven Palo Alto Networks' role as a cybersecurity vendor, the company is subject to intense scrutiny from potential customers and is a target for a variety of threat actors. Recognizing that a product security incident could have an enormous impact on customers, Palo Alto Networks considers cybersecurity and product integrity an implicit corporate mandate. All products are subject to the company's end-to-end product security framework (E2E Framework). The framework is designed to provide defense in depth for each stage of the product lifecycledesign, sourcing, manufacturing, fulfilment, and service. Each stage is independently evaluated to determine security risks, and domain experts select relevant public standards and best practices to target those risks. Selected standards include the Federal Information Processing Standards (FIPS) i , Common Criteria ii , and the United Kingdom's Commercial Product Assurance (CPA) iii ."}], "metadata": {"source": "Case Studies in Cyber Supply Chain Risk Management_ Palo Alto Networks, Inc.", "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 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": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 1}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to Cell Phone Forensic Tools_ an Overview and Analysis Update:\n\nther Paraben's Toolbox or a compatible cable (e.g., datapilot) to establish a data-link between the phone and the forensic workstation. The type of phone being acquired determines the cable interface.\nSerial RS-232 and USB data-link connections are established via the phone data port or the under-battery interface connection. Device Seizure uses the MD5 hash function to protect the integrity of acquired files. Additional features include bookmarking of information to be filtered and organized in a report format, searching for text strings within the acquired data, and automatically assembling found images under a single facility."}], "metadata": {"source": "Cell Phone Forensic Tools_ an Overview and Analysis Update", "cmmc_level": "all", "cmmc_domain": "System and Information Integrity", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Recommendation for Key Derivation Using Pseudorandom Functions:\n\nThe Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation's measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL's responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national 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": "Recommendation for Key Derivation Using Pseudorandom Functions", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Codes for Identification of Federal and Federally-Assisted Organizations:\n\n| | 12B7 | USDA, Office of the Judicial Officer | | 12B8 | USDA, Board of Contract Appeals ` | | 12BD | USDA, Office of Ethics | | 1215 | USDA, Office of Operations | | 12B0 | USDA, Assistant Secretary for Administration | | 12C0 | Under Secretary for Natural Resources and Environment | | 12C2 | Forest Service | | 12C3 | Natural Resources Conservation Service | | 12D0 | Under Secretary for Farm and Foreign Agricultural Services | | 12D2 | Farm Service Agency | | 12D3 | Foreign Agricultural Service | | 12D4 | Risk Management Agency | | 1263 | Federal Crop Insurance Corporation | | 1260 | Commodity Credit Corporation | | 12E0 | Under Secretary for Rural Development |"}], "metadata": {"source": "Codes for Identification of Federal and Federally-Assisted 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 Module-Lattice-Based Key-Encapsulation Mechanism Standard provide? (Part 2)"}, {"role": "assistant", "content": "the Module Learning with Errors problem. At present, ML-KEM is believed to be secure, even against adversaries who possess a quantum computer. This standard specifies three parameter sets for ML-KEM.\nIn order of increasing security strength and decreasing performance, these are ML-KEM-512, ML-KEM-768, and ML-KEM-1024. Keywords: computer security; cryptography; encryption; Federal Information Processing Standards; key-encapsulation mechanism; lattice-based cryptography; post-quantum; public-key cryptography. ## Federal Information Processing Standards Publication 203\n\nPublished:\n\nAugust 13, 2024\n\nEffective:\n\nAugust 13, 2024\n\n## Announcing the\n\n## Module-Lattice-Based Key-Encapsulation Mechanism Standard\n\nFederal Information Processing Standards (FIPS) publications are developed by the National Institute of Standards and Technology (NIST) under 15 U.S.C. 278g-3 and issued by the Secretary of Commerce under 40 U.S.C. 11331. 1. Name of Standard. Module-Lattice-Based Key-Encapsulation Mechanism Standard (FIPS 203). 2. Category of Standard. Computer Security. Subcategory. Cryptography. 3. Explanation. A cryptographic key (or simply 'key') is represented in a computer as a string of bits. A shared secret key is a cryptographic key that is computed jointly by two parties (e.g., Alice and Bob) using a set of algorithms. Under certain conditions, these algorithms ensure that both parties will produce the same key and that this key is secret from adversaries. Such a shared secret key can then be used with symmetric-key cryptographic algorithms (specified in other NIST standards) to perform tasks such as encryption and authentication of digital information. This standard specifies a set of algorithms for establishing a shared secret key. While there are many methods for establishing a shared secret key, the particular method described in this standard is a key-encapsulation mechanism (KEM)."}], "metadata": {"source": "Module-Lattice-Based Key-Encapsulation Mechanism Standard", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Guidelines for Smart Grid Cybersecurity provide? (Part 3)"}, {"role": "assistant", "content": "framework that organizations can use to develop effective cybersecurity strategies tailored to their\nparticular combinations of smart grid-related characteristics, risks, and vulnerabilities.\nOrganizations in the diverse community of smart grid stakeholders—from utilities to providers of\nenergy management services to manufacturers of electric vehicles and charging stations—can\nuse the methods and supporting information presented in this report as guidance for assessing\nrisk and identifying and applying appropriate security requirements. This approach recognizes\nthat the electric grid is changing from a relatively closed system to a complex, highly\ninterconnected environment. Each organization’s cybersecurity requirements should evolve as\ntechnology advances and as threats to grid security inevitably multiply and diversify. advanced metering infrastructure; architecture; cryptography; cybersecurity; electric grid;\nprivacy; security requirements; smart grid\n\nKeywords\n\n\fACKNOWLEDGMENTS\n\nThis revision to the NISTIR was developed by members of the Smart Grid Interoperability Panel\n(SGIP) Smart Grid Cybersecurity Committee (SGCC) (formerly the Cyber Security Working\nGroup (CSWG)), which is chaired by Victoria Yan Pillitteri (NIST). Dave Dalva (Stroz\nFriedberg), Akhlesh Kaushiva (Department of Energy), and Scott Saunders (Sacramento\nMunicipal Utility District) are the vice chairs and Mark Enstrom (Neustar) and Amanda Stallings\n(Ohio PUC) have served as the secretary. Tanya Brewer of NIST is the lead editor of this report. A special note of thanks goes to the subgroup leads, Frances Cleveland (Xanthus Consulting\nInternational), Nelson Hastings (NIST), Rebecca Herold (Rebecca Herold & Associates, LLC),\nElizabeth Sisley (Calm Sunrise Consulting, LLC), and Doug McGinnis (Exelon) who along with\ntheir subgroup team members contributed significantly to this revision."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 2}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS):\n\naccess control; confidentiality; cryptographic key management system; disaster recovery; federal cryptographic key management system; integrity; metadata; security assessment; security functions; security policies; source authentication."}], "metadata": {"source": "A Profile for U.S. Federal Cryptographic Key Management Systems (CKMS)", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0:\n\n2 A complete development archive can be found at https://www.nist.gov/privacy-framework. | Executive Summary............................................................................................................................... i | Executive Summary............................................................................................................................... i | Executive Summary..............................................................................................................................."}], "metadata": {"source": "NIST Privacy Framework_ A Tool for Improving Privacy Through Enterprise Risk Management, Version 1.0", "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 Practical Combinatorial Testing:\n\n## 3.3.1 Invalid Combinations and Constraints\n\n## 3.3.2 Cost Factors\n\n- the subject is an employee AND current time is between 9 am and 5 pm AND it is not a weekend\n- OR subject is an employee with a special authorization code\n- OR subject is an auditor AND the time is between 9 am and 5 pm (not constrained to weekdays)."}], "metadata": {"source": "Practical Combinatorial Testing", "cmmc_level": "all", "cmmc_domain": "Audit and Accountability", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry:\n\n- -NISTIR 7622, Notional Supply Chain Risk Management Practices for Federal Information Systems , 2012 [NISTIR 7622] - -NIST Special Publication (SP) 800-161, Supply Chain Risk Management Practices for Federal Information Systems and Organizations , 2015 [SP 800-161] - -NIST SP 800-37 Revision 2, Risk Management Framework for Information Systems and Organizations, 2018 [SP800-37] - -NIST SP 800-53, Revision 5, Security and Privacy Controls for Information Systems and Organizations , 2020 [SP 800-53] - -Relevant controls and control enhancements include: -  Supply Chain Risk Management Control Family (SR) -  Supply Chain Risk Management Strategy (PM-30) -  Suppliers of Critical or Mission Essential Items (PM-30(1)) -  Integrated Situational Awareness (SI-4(17)) -  External System Services (SA-9) -  Acquisition Process (SA-4) -  Supply Chain Risk Assessment (RA-3(1)) -  Criticality Analysis (RA-9) -  Incident Handling - Supply Chain Coordination (IR-4(10)) -  Incident Reporting - Supply Chain Coordination (IR-6(3)) -  Controlled Maintenance (MA-2) -  Tamper Protection (PE-3(5)) - -Case studies, briefing papers, and other resources on the NIST Cyber Supply Chain Risk Management site [NIST C-SCRM]: 7 - -Case Studies: Best Practices in Cyber Supply Chain Risk Management, 2015 - -Best Practices in"}], "metadata": {"source": "Key Practices in Cyber Supply Chain Risk Management_ Observations from Industry", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Physical Protection?"}, {"role": "assistant", "content": "According to Glossary of Key Information Security Terms:\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": "Glossary of Key Information Security Terms", "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 Stateless Hash-Based Digital Signature Standard:\n\n```\n1: if |𝑐𝑡𝑥| > 255 then 2: return ⊥ ▷ return an error indication if the context string is too long 3: end if $ 4: 𝑎𝑑𝑑𝑟𝑛𝑑 ← -𝔹 𝑛 ▷ skip lines 4 through 7 for the deterministic variant 5: if 𝑎𝑑𝑑𝑟𝑛𝑑 = NULL then 6: return ⊥ ▷ return an error indication if random bit generation failed 7: end if 8: switch PH do 9: case SHA-256: 10: OID ← toByte (0 x0609608648016503040201 , 11) ▷ 2.16.840.1.101.3.4.2.1 11: PH 𝑀 ← SHA-256 (𝑀) 12: case SHA-512: 13: OID ← toByte (0 x0609608648016503040203 , 11) ▷ 2.16.840.1.101.3.4.2.3 14: PH 𝑀 ← SHA-512 (𝑀) 15: case SHAKE128: 16: OID ← toByte (0 x060960864801650304020B , 11) ▷ 2.16.840.1.101.3.4.2.11 17: PH 𝑀 ← SHAKE128 (𝑀, 256) 18: case SHAKE256: 19: OID ← toByte (0 x060960864801650304020C , 11) ▷ 2.16.840.1.101.3.4.2.12 20: PH 𝑀 ← SHAKE256 (𝑀, 512) 21: case … ▷ other approved hash functions or XOFs 22: … 23: end switch 24: 𝑀 ′ ← toByte (1, 1) ∥ toByte (|𝑐𝑡𝑥|, 1) ∥ 𝑐𝑡𝑥 ∥ OID ∥ PH 𝑀 25: SIG ← slh _ sign _ internal (𝑀 ′ , SK , 𝑎𝑑𝑑𝑟𝑛𝑑) ▷ omit 𝑎𝑑𝑑𝑟𝑛𝑑 for the deterministic variant 26: return SIG\n```\n\n```\n1: if |𝑐𝑡𝑥| > 255 then 2: return false 3: end if 4: switch PH do 5: case SHA-256: 6: OID ← toByte (0 x0609608648016503040201 , 11) ▷ 2.16.840.1.101.3.4.2.1 7: PH 𝑀 ← SHA-256 (𝑀) 8: case SHA-512: 9: OID ← toByte (0 x0609608648016503040203 , 11) ▷ 2.16.840.1.101.3.4.2.3 10: PH 𝑀 ← SHA-512 (𝑀) 11: case SHAKE128: 12: OID ← toByte (0 x060960864801650304020B , 11) ▷ 2.16.840.1.101.3.4.2.11 13: PH 𝑀 ← SHAKE128 (𝑀, 256) 14: case SHAKE256: 15: OID ← toByte (0 x060960864801650304020C , 11) ▷ 2.16.840.1.101.3.4.2.12 16: PH 𝑀 ← SHAKE256 (𝑀, 512) 17: case … ▷ other approved hash functions or XOFs 18: … 19: end switch 20: 𝑀 ′ ← toByte (1, 1) ∥ toByte (|𝑐𝑡𝑥|, 1) ∥ 𝑐𝑡𝑥 ∥ OID ∥ PH 𝑀 21: return slh _ verify _ internal (𝑀 ′ , SIG , PK )\n```"}], "metadata": {"source": "Stateless Hash-Based Digital Signature Standard", "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 Guide to Computer Security Log Management:\n\n| 5.3 | Respond to Identified Events................................................................................. | 5-8 |\n|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--------------------|\n| 5.4 | Manage Long-Term Log Data Storage .................................................................. | 5-9 |\n| 5.5 | Provide Other Operational Support...................................................................... | 5-10 |\n| 5.6 | Perform Testing and Validation ........................................................................... | 5-10 |\n| 5.7 | Summary............................................................................................................."}], "metadata": {"source": "Guide to Computer Security Log Management", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases:\n\nFor example, LoJax, discovered in August 2018, manifests itself in UEFI malware, allowing it to continuously persist in the firmware layer despite operating system (OS) reinstallations, and thus remain invisible to standard kernel-based virus scans [1]. These attacks can be devastating to cloud environments because they often require server-by-server rebuilds or replacements, which can take weeks. Although still rare, these attacks are increasing as attackers become more sophisticated.\n\nVM isolation can be used to help protect workloads in multi-tenant environments like public and hybrid clouds. Isolating entire VMs translates to protection against malicious insiders at the cloud provider, or malware exposure and data leakage to other tenants with workloads running on the same platform. Many modern cloud deployments use VMs as container worker nodes. This provides a highly consistent and scalable way to deploy containers regardless of the underlying physical platforms. With full VM isolation, the virtual workers hosting container\n\n'UEFI Secure Boot (SB) is a verification mechanism for ensuring that code launched by a computer's UEFI firmware is trusted' [19]. SB prevents malware from taking 'advantage of several pre-boot attack points, including the system-embedded firmware itself, as well as the interval between the firmware initiation and the loading of the operating system' [20]."}], "metadata": {"source": "Hardware-Enabled Security_ Enabling a Layered Approach to Platform Security for Cloud and Edge Computing Use Cases", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Access Control?"}, {"role": "assistant", "content": "According to Prioritizing Cybersecurity Risk for Enterprise Risk Management:\n\n| Executive Summary............................................................................................................................1 |\n|------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction...................................................................................................................................4 |\n| 2. Cybersecurity Risk Considerations ..................................................................................................9 |\n| 2.2.1. Factors Influencing Prioritization ................................................................................................12 |\n| 2.2.2. Cybersecurity Risk Optimization .................................................................................................12 |\n| 2.2.3. Cybersecurity Risk Priorities at Each Enterprise Level................................................................14 |\n| 2.2.4. Considerations of Positive Risks as an Input to ERM..................................................................15 |\n| 2.2.5. Visualizing Risk Priority ...............................................................................................................16 |\n| 2.3.1. Risk Acceptance...........................................................................................................................21 |\n| 2.3.2. Risk Avoidance ............................................................................................................................22 |\n| 2.3.3. Risk Transfer................................................................................................................................22 |\n| 2.3.4."}], "metadata": {"source": "Prioritizing Cybersecurity Risk for Enterprise Risk Management", "cmmc_level": "all", "cmmc_domain": "Access Control", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n| Subcategory | Applicability to the Ground Segment | References | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | ID.BE-4 : Dependencies and critical functions for delivery of critical services are established | Organizations should identify any critical capabilities from other sectors such as power, transportation, communications, timing etc."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Risk Assessment?"}, {"role": "assistant", "content": "According to Verification and Test Methods for Access Control Policies_Models:\n\nIII | |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------| | 1 INTRODUCTION ...................................................................................................1 | 1 INTRODUCTION ...................................................................................................1 | 1 INTRODUCTION ...................................................................................................1 | | 1.1 Authority..........................................................................................................................1 1.2 Document Scope and Purpose | 1.1 Authority..........................................................................................................................1 1.2 Document Scope and Purpose | .........................................................................................1 | | 1.3 Audience and Assumptions..............................................................................................2 | 1.3 Audience and Assumptions..............................................................................................2 | | | 1.4 Document Organization...................................................................................................2 | 1.4 Document Organization...................................................................................................2 | | | 2 ACCESS CONTROL POLICIES AND MODELS .......................................................3 | 2 ACCESS CONTROL POLICIES AND MODELS .......................................................3 | 2 ACCESS CONTROL POLICIES AND MODELS .......................................................3 | | 2.1 Access Control Policies ...................................................................................................3 | 2.1 Access Control Policies ...................................................................................................3 | | | 2.2 AC Models.......................................................................................................................5 | 2.2 AC Models.......................................................................................................................5 | | | 3 ACCESS CONTROL SAFETY AND FAULTS ...........................................................8 | 3 ACCESS CONTROL SAFETY AND FAULTS ...........................................................8 | 3 ACCESS CONTROL SAFETY AND FAULTS ...........................................................8 | | 3.1 Safety | 3.1 Safety | | | ...............................................................................................................................8 3.2 AC Faults .........................................................................................................................8 | ...............................................................................................................................8 3.2 AC Faults .........................................................................................................................8 | | | 3.3 Multi-policies considerations...........................................................................................9 | 3.3 Multi-policies considerations...........................................................................................9 | | | 3.4 Vulnerability Hierarchies in Access Control Configurations ........................................10 | 3.4 Vulnerability Hierarchies in Access Control Configurations ........................................10 | | | 4 POLICY VERIFICATION PRINCIPLES.................................................................15 | 4 POLICY VERIFICATION PRINCIPLES.................................................................15 | | | 4.1 Model Verification.........................................................................................................15 |"}], "metadata": {"source": "Verification and Test Methods for Access Control Policies_Models", "cmmc_level": "all", "cmmc_domain": "Risk Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Services Acquisition?"}, {"role": "assistant", "content": "According to Implementation of DevSecOps for a Microservices-based Application with Service Mesh:\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. Cloud-native applications have evolved into a standardized architecture consisting of multiple loosely coupled components called microservices (often typically implemented as containers) that are supported by an infrastructure for providing application services, such as service mesh. Both of these components are usually hosted on a container orchestration and resource management platform."}], "metadata": {"source": "Implementation of DevSecOps for a Microservices-based Application with Service Mesh", "cmmc_level": "all", "cmmc_domain": "System and Services Acquisition", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems:\n\n|\n| Table 1.\nTechnical cybersecurity capability recommendations...........................................................14 |\n| Table 2. Non-technical cybersecurity capability recommendations....................................................19 |\n| Table 3. Characteristics of tested inverters .......................................................................................28 |\n| Table 4. Guideline #1 testing results .................................................................................................28 |\n| Table 5. Guideline #2 testing results .................................................................................................29 |\n| Table 6. Guideline #3 testing results .................................................................................................29 |\n| Table 7. Guideline #4 testing results .................................................................................................30 |\n| Table 8."}], "metadata": {"source": "Cybersecurity for Smart Inverters_ Guidelines for Residential and Light Commercial Solar Energy Systems", "cmmc_level": "all", "cmmc_domain": "Security Assessment", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Assessing Federal and Commercial Information Security Needs:\n\nThe U.S. government has been involved in developing security technology for computer and communications security for some time.\n\nThe NIST study team met with 28 organizations -17 federal agencies, 10 commercial organizations, and 1 state government. Fourteen of the organizations were in the Washington/Baltimore area and 14 were outside of this area, and included Arizona, California, New Jersey, New York, Pennsylvania, and Texas. Companies representing energy, financial, communications, insurance, manufacturing, computers, and service were included. Of the federal organizations, both the executive and judicial branches were represented. Activities included law enforcement, benefits delivery, nuclear/energy, space exploration, defense, tax system, information collection and dissemination, air traffic, and service center operations. Contractors participated in a number of the federal agency meetings. State functions represented included justice, transportation, lottery, franchise tax, health and welfare, motor vehicles, controllers office, and data center operations.\n\nThe study team found that most commercial organizations take a carefully measured and cost-effective approach to computer and communications security issues. Each commercial organization interviewed described computer security as an important and necessary capability of their computer systems. However, such statements were quickly caveated with the reality that a business case is also presented regarding the merits of such capabilities. This business case was described as balancing the:"}], "metadata": {"source": "Assessing Federal and Commercial Information Security Needs", "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 Guide to IPsec VPNs:\n\n1. Identify Needs - Identify the need to protect network communications and determine how that need can best be met. 2. Design the Solution - Make design decisions in several areas, including architectural considerations, authentication methods, cryptographic policy, and packet filters. The placement of an IPsec gateway has potential security, functionality, and performance implications. An authentication solution should be selected based primarily on maintenance, scalability, and security. Packet filters should apply appropriate protections to traffic and not protect other types of traffic for performance or functionality reasons. 3. Implement and Test a Prototype - Test a prototype of the designed solution in a lab or test environment to identify any potential issues. Testing should evaluate several factors, including connectivity, protection, authentication, application compatibility, management, logging, performance, the security of the implementation, and component interoperability. 4. Deploy the Solution - Gradually deploy IPsec throughout the enterprise."}], "metadata": {"source": "Guide to IPsec VPNs", "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 Understanding Stablecoin Technology and Related Security Considerations:\n\nir pegged asset, currency, or index. This is in great contrast to most cryptocurrencies (e.g., Bitcoin) whose value experiences significant volatility and whose price is dictated by supply and demand.\nUnlike other cryptocurrencies, there is no expectation of earnings through holding stablecoins (unless the pegged asset is expected to rise in value over time). However, even stablecoins with no expectation of earnings can themselves be invested in decentralized finance products that do promise to yield returns."}], "metadata": {"source": "Understanding Stablecoin Technology and Related Security Considerations", "cmmc_level": "all", "cmmc_domain": "Physical Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Security Assessment?"}, {"role": "assistant", "content": "According to 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 does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance:\n\ncapabilities required from IoT devices and their manufacturers, respectively, as well as associated documentation to round out the guidance provided by the program. The documents are complemented by an online catalog [CATALOG] of detailed technical capabilities and supporting non-technical capabilities, updates that were published in March of 2021.\n\n- Smart Door Lock: Federal organizations may utilize connected door locks that can scan PIV cards and manage access to and within facilities.\n- Unmanned Aircraft System (UAS): Federal organizations could use UAS to inspect facilities as part of monitoring and maintenance of the facility.\n- Water Sensors: Some federal organizations may use connected IoT environment sensors to monitor various aspects of facilities.\n\nMr. Fagan concluded by briefly reviewing updates to the online IoT device cybersecurity capabilities catalog and encouraging workshop participants to provide input and feedback on the catalog's contents and utility."}], "metadata": {"source": "Summary Report for the Virtual Workshop Addressing Public Comment on NIST Cybersecurity for IoT Guidance", "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 Supply Chain Risk Management?"}, {"role": "assistant", "content": "According to Guide to Cyber Threat Information Sharing:\n\n- Experienced cybersecurity personnel,\n- Members and operators of established threat information sharing organizations,\n- Trusted business associates, supply chain partners, and industry peers, and\n- Personnel knowledgeable about legal issues, internal business processes, procedures, and systems.\n\nmay be based on geographic region, political boundary, industrial sector, business interest, or threat space (e.g., focused on phishing attacks). Many of these communities have multinational constituencies and global reach. Examples of potential sharing partners are ISACs, domestic and foreign Computer Emergency Readiness Teams (CERTs) or CSIRTs, Information Sharing and Analysis Organizations (ISAOs), DHS Automated Indicator Sharing (AIS) initiative, threat and vulnerability repositories, law enforcement agencies, product vendors, managed security service providers, internet service providers, supply chain partners, industry sector peers, business partners, and customers."}], "metadata": {"source": "Guide to Cyber Threat Information Sharing", "cmmc_level": "all", "cmmc_domain": "Supply Chain Risk Management", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Audit and Accountability?"}, {"role": "assistant", "content": "According to Secure Hash Standard (SHS):\n\n1. Set the initial hash value, H (0) , as specified in Sec. 5.3.3.\n2. The message is padded and parsed as specified in Section 5."}], "metadata": {"source": "Secure Hash Standard (SHS)", "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 Guide for Conducting Risk Assessments:\n\nsments at whatever frequency deemed appropriate. Organizations can also attempt to capture changes in the effectiveness of risk response measures in order to maintain the currency of risk assessments.\nThe objective is to maintain an ongoing situational awareness of the organizational governance structures and activities, mission/business processes, information systems, and environments of operation, and thereby all of the risk factors that may affect the risk being incurred by organizations. Therefore, in applying the risk assessment context or risk frame (i.e., scope, purpose, assumptions, constraints, risk tolerances, priorities, and trade-offs), organizations consider the part risk factors play in the risk response plan executed. For example, it is expected to be quite common for the security posture of information systems (that is, the risk factors measured within those systems) to reflect only a part of the organizational risk response, with response actions at the organization level or mission/business process level providing a significant portion of that response. In"}], "metadata": {"source": "Guide for Conducting Risk Assessments", "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 Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies:\n\ns for an other than authorized purposes, have access or potential |\n\n| | access to sensitive information, whether physical or electronic.\n|\n|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Categorization | The process of determining the security category for information or an information system. Security categorization methodologies are described in CNSS Instruction 1253 for national security systems and in FIPS Publication 199 for other than national security systems. |\n| Ciphertext | Data in its encrypted form. |\n| Confidentiality | The property that sensitive information is not disclosed to unauthorized entities. |\n| Critical Infrastructure | The essential services that support a society and serve as the backbone for the society's economy, security and health. |\n| Cryptographic algorithm | A well-defined computational procedure that takes variable inputs, including a cryptographic key (if applicable), and produces an output. |\n| Cryptographic Key | A parameter used in conjunction with a cryptographic algorithm that determines its operation in such a way that an entity with knowledge of the key can reproduce or reverse the operation, while an entity without knowledge of the key cannot. |\n| Cryptography | The science of information hiding and verification. It includes the protocols, algorithms and methodologies to securely and consistently prevent unauthorized access to sensitive information and enable verifiability of the information."}], "metadata": {"source": "Guideline for Using Cryptographic Standards in the Federal Government_ Directives, Mandates and Policies", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Maintenance?"}, {"role": "assistant", "content": "According to Recommendation for Block Cipher Modes of Operation_ the CMAC Mode for Authentication:\n\nMay 2005 INCLUDES UPDATES AS OF 10-06-2016: PAGE II\n\nThe following changes have been incorporated into Special Publication 800-38B. Errata updates include corrections, clarifications, or other minor changes in the publication that are either editorial or substantive in nature."}], "metadata": {"source": "Recommendation for Block Cipher Modes of Operation_ the CMAC Mode for Authentication", "cmmc_level": "all", "cmmc_domain": "Maintenance", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Incident Response?"}, {"role": "assistant", "content": "According to Guide to Malware Incident Prevention and Handling for Desktops and Laptops:\n\n## Guide to Malware Incident Prevention and Handling for Desktops and Laptops\n\n## Guide to Malware Incident Prevention and Handling for Desktops and Laptops\n\nMalware, also known as malicious code, refers to a program that is covertly inserted into another program with the intent to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim's data, applications, or operating system. Malware is the most common external threat to most hosts, causing widespread damage and disruption and necessitating extensive recovery efforts within most organizations. This publication provides recommendations for improving an organization's malware incident prevention measures. It also gives extensive recommendations for enhancing an organization's existing incident response capability so that it is better prepared to handle malware incidents, particularly widespread ones."}], "metadata": {"source": "Guide to Malware Incident Prevention and Handling for Desktops and Laptops", "cmmc_level": "all", "cmmc_domain": "Incident Response", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Personnel Security?"}, {"role": "assistant", "content": "According to Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control:\n\n| Subcategory | Applicability to the Ground Segment | References | |--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Identify: Asset Management Category The data, personnel, devices, systems, and facilities that enable the organization to achieve its business objectives are identified and managed in a manner that is consistent with their importance to organizational objectives and the organization's risk strategy."}], "metadata": {"source": "Satellite Ground Segment_ Applying the Cybersecurity Framework to Satellite Command and Control", "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.10 (NIST 3.2.10)?"}, {"role": "assistant", "content": "According to Digital Identity Guidelines_ Authentication and Authenticator Management:\n\n3.2.10. 3.2.10\n\n4. 3.2.10."}], "metadata": {"source": "Digital Identity Guidelines_ Authentication and Authenticator Management", "cmmc_level": "all", "nist_control": "3.2.10", "cmmc_practice_id": "AT.L2-3.2.10", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What additional guidance does Cell Phone Forensic Tools_ an Overview and Analysis Update provide? (Part 5)"}, {"role": "assistant", "content": "nvestigation involving cell phones and PDA phones, or construed as legal advice. Its purpose is to inform readers of the various technologies available and areas for consideration when employing them.\nBefore applying the material in this report, readers are advised to consult with management and legal officials for compliance with laws and regulations (i.e., local, state, federal, and international) that pertain to their situation. · For more information on this effort see www.cftt.nist.gov\n\n## Audience\n\nThe primary audience of the Cell Phone Forensic Tool document is law enforcement, incident response team members, and forensic examiners who are responsible for conducting forensic procedures related to cell phone devices and associated removable media. ## Table of Contents\n\n| INTRODUCTION......................................................................................................................... | 1 |\n|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|\n| BACKGROUND........................................................................................................................... | 3 |\n| SUBSCRIBER IDENTITY MODULE.................................................................................................."}], "metadata": {"source": "Cell Phone Forensic Tools_ an Overview and Analysis Update", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Communications Protection?"}, {"role": "assistant", "content": "According to Guidelines for Managing the Security of Mobile Devices in the Enterprise:\n\n| 4.1.2. | Data Isolation Mechanisms....................................................................................16 | |\n|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|\n| 4.1.3. | Platform Management APIs...................................................................................17 | |\n| 4.1.4. | VPN Support..........................................................................................................17 | |\n| 4.1.5. | Authentication Mechanisms...................................................................................17 | |\n| Enterprise Mobile Security Technologies...................................................................18 | Enterprise Mobile Security Technologies...................................................................18 | |\n| 4.2.1. | Enterprise Mobility Management............................................................................18 | |\n| 4.2.2."}], "metadata": {"source": "Guidelines for Managing the Security of Mobile Devices in the Enterprise", "cmmc_level": "all", "cmmc_domain": "System and Communications Protection", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for Identification and Authentication?"}, {"role": "assistant", "content": "According to A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications:\n\nThe need for random and pseudorandom numbers arises in many cryptographic applications. For example, common cryptosystems employ keys that must be generated in a random fashion. Many cryptographic protocols also require random or pseudorandom inputs at various points, e.g., for auxiliary quantities used in generating digital signatures, or for generating challenges in authentication protocols."}], "metadata": {"source": "A Statistical Test Suite for Random and Pseudorandom Number Generators for Cryptographic Applications", "cmmc_level": "all", "cmmc_domain": "Identification and Authentication", "type": "domain_guidance"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC Level 3 require for Identification and Authentication?"}, {"role": "assistant", "content": "According to Security Requirements for Cryptographic Modules:\n\ne/firmware security; operating environment; physical security; non-invasive security; sensitive security parameter management; self-tests; life-cycle assurance; and mitigation of other attacks.\nThis standard supersedes FIPS 140-2, Security Requirements for Cryptographic Modules , in its entirety."}], "metadata": {"source": "Security Requirements for Cryptographic Modules", "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 is CMMC practice AC.L2-3.1.11 (NIST 3.1.11)?"}, {"role": "assistant", "content": "According to Guidelines for Smart Grid Cybersecurity:\n\n3.1.11 Password Management Vulnerability (CWE-255)\n\nDescription\n\nPasswords are the most commonly used form of authentication."}], "metadata": {"source": "Guidelines for Smart Grid Cybersecurity", "cmmc_level": "all", "nist_control": "3.1.11", "cmmc_practice_id": "AC.L2-3.1.11", "type": "control"}} {"messages": [{"role": "system", "content": "You are a CMMC (Cybersecurity Maturity Model Certification) expert with deep knowledge of NIST SP 800-171, SP 800-172, and defense contractor cybersecurity requirements. You provide accurate guidance on CMMC compliance, CUI protection, and DoD security controls."}, {"role": "user", "content": "What does CMMC require for System and Information Integrity?"}, {"role": "assistant", "content": "According to BIOS Protection Guidelines for Servers:\n\n| Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 | Executive Summary................................................................................................................. 1 |\n|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|\n| 1. Introduction.................................................................................................................... | 1. Introduction...................................................................................................................."}], "metadata": {"source": "BIOS Protection Guidelines for Servers", "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 Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings 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. National Institute of Standards and Technology Attn: Applied Cybersecurity Division, Information Technology Laboratory 100 Bureau Drive (Mail Stop 2000) Gaithersburg, MD 20899-2000 Email: 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\nThis report provides an overview of the topics discussed at the 'Internet of Things (IoT) Cybersecurity Colloquium' hosted on NIST's campus in Gaithersburg, Maryland on October 19, 2017. It summarizes key takeaways from the presentations and discussions. Further, it provides information on potential next steps for the NIST Cybersecurity for IoT Program."}], "metadata": {"source": "Internet of Things (IoT) Cybersecurity Colloquium_ A NIST Workshop Proceedings", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Maintenance", "System and Communications Protection", "Security Assessment", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "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 Annual Report 2018_ NIST_ITL Cybersecurity Program provide? (Part 5)"}, {"role": "assistant", "content": "most noteworthy cybersecurity achievements in 2018 and offers insights into our current priorities and strategies. For a more complete review of our work, check out our primary cybersecurity website.\n2\n\nNIST welcomes all suggestions for how we can improve our cybersecurity work to better serve the public and private sectors. And, by all means, please join us as we pick up the pace. Donna F. Dodson NIST Chief Cybersecurity Advisor\n\n\n\n1/emspace Federal Information Processing Standard (FIPS) 140-3, https:/ /csrc.nist.gov/publications/detail/fips/140/3/final\n\n2/emspace NIST Cybersecurity, https:/ /www.nist.gov/topics/cybersecurity\n\n## TABLE OF CONTENTS\n\n| Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . | . 1 |\n|------------------------------------------------------------------------------------------------------------------------------------|-------|\n| Imperative 1 - Advancing Cybersecurity and Privacy Standards . . . . . . | 3 |\n| Imperative 2 - Enhancing Risk Management . . . . . . . . . . . . . . . . . | 5 |\n| Imperative 3 - Strengthening Cryptographic Standards and Validation . | 8 |\n| Imperative 4 - Advancing Cybersecurity Research and Applications Development . . . . . . . . . . . . . . . . | 12 |\n| Imperative 5 - Improving Cybersecurity Awareness, Training, Education, and Workforce Development . . . . . . . . . . . . . . . . . | 15 |\n| Imperative 6 - Enhancing Identity and Access Management . . . . . . . . | 19 |\n| Imperative 7 - Bolstering Infrastructure Protection . . . . . . . . . . . . . | 21 |\n| Imperative 8 - Securing Emerging Technologies . . . . . . . . . . . . . . . | 24 |\n| Imperative 9 - Advancing Security Test and Measurement Tools . . . . . | 29 |\n\n## THIS PAGE IS INTENTIONALLY LEFT BLANK\n\n## INTRODUCTION\n\nIt is often said that cybersecurity is about people, process, and technology."}], "metadata": {"source": "Annual Report 2018_ NIST_ITL Cybersecurity Program", "cmmc_level": "all", "cmmc_domains": ["Planning", "System and Services Acquisition", "Physical Protection", "Awareness and Training", "Incident Response", "Supply Chain Risk Management", "Configuration Management", "Maintenance", "Security Assessment", "System and Communications Protection", "Media Protection", "Risk Assessment", "Audit and Accountability", "Personnel Security", "Identification and Authentication", "Access Control", "System and Information Integrity"], "type": "semantic_chunk", "chunk_id": 4}}